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.
|Replies are listed 'Best First'.|
Re: Re: Re: Encapsulation through stringification - a variation on flyweight objects
by theorbtwo (Prior) on Apr 02, 2003 at 05:12 UTC