April 5, 2012
8:13 a.m.
+ 1
In fact, presently use of become is not considered good OOP so at first my humble suggestion is you consider revising the whole architecture in order to understand why you need such a thing and find a better [design] pattern.
there is no other way to represent an object by proxy, which is not yet in memory, but loaded on demand. otherwise you will be forced to make an outer object (which refers to a proxy), to know it and replace a reference to it with another object.
And this seems like precisely one of those times you really do want to reach into the magic toolbox for #become:. Sometimes you really do need it.