object Graph
{
// public operations to create ADT instances
}
final class Graph[Key, A] private(rep: SortedMap[Key, (A,
(SortedSet[Key], SortedSet[Key]))])
{
// implementation with access to rep
}
The main thing is the private in this odd position, which is
On Sat, 14 Apr 2012, Lars Hupel wrote:
The main thing is the private in this odd position, which is Odersky's
way to make the constructor private, but the keep the type itself
public. This detail seems to have been forgotten in Java -- in fact in a
recent talk some Java guru admitted that --
I've heard of this recent addition to the OO vocabulary to fix some
early conceptual problems of the approach. That is object Graph part
only.
How would a Java person solve the private constructor problem?
Could you explain a bit more? -- Java has private constructors.
The source file
On Fri, 13 Apr 2012, Lukas Bulwahn wrote:
Since (2) is nothing specifically exciting by JUNG either -- it seems
to be based on plain Java Graphics2D stuff -- I had recommended to
abandon JUNG altogether. Did anything happen here in the meantime?
We have discussed internally in more detail