in reply to
Re: Encapsulation through stringification - a variation on flyweight objects
in thread Encapsulation through stringification - a variation on flyweight objects
I thought it would be a bit too much to have been the first to think of this <g>. I had super searched but not on 'Inside-Out objects'.
I know about the memory leak, I have not included a DESTROY method as this was just an example (the same reason I have not included any accessors, or attribute validation). It's still a valid point though.
Stringification overload is indeed problematic. One hole poked ;).
Thx for the comment.