Community
Participate
Working Groups
I can't think of any benefit for clients to create new instances of InstanceScope. We should add a singleton field so clients don't have to create a new instance: InstanceScope.INSTANCE.getNode(...) instead of new InstanceScope().getNode(...)
That applies to all 4 subclasses of AbstractScope.
Created attachment 185455 [details] patch
Patch released to HEAD.
Any reason for not deprecating the constructors?
Just waiting for the new year so I could update the copyrights to 2011. ;-) Released to HEAD.
And here I was writing a comment about how you marked this as "@since 3.4" instead of "@since 3.7" ... without realizing equinox does not follow the numbering of the Eclipse platform :p. I broke the compatibility of my project with Eclipse 3.5 and Eclipse 3.6 by using this new singleton thinking the @since was enough reason for me to do it without checking too much into it... Now I just have to pay chocolate to my team (http://model-driven-blogging.blogspot.com/2008/01/chocolate-commit.html) and pay a little more attention in the future :p.
(In reply to comment #6) > And here I was writing a comment about how you marked this as "@since 3.4" > instead of "@since 3.7" ... without realizing equinox does not follow the > numbering of the Eclipse platform :p. > It not that we don't follow the numbering of the Eclipse platform. It is because all of our bundles are versioned independently. You will find that there are a number of other bundles in the eclipse platform for 3.7 that are not versioned at 3.7 either.