On 16 Jul 2009, at 09:30, Richard Frith-Macdonald wrote:
But ... going back to the issue of avoiding changes to ivars breaking ABI in future releases ... the approach I currently favor is having a *single* ivar in the public class. This is a private id variable referring to an instance of a private class which is used to hold the real ivars.
I really don't like this approach. It makes the code difficult to read, destroys locality of reference, and hurts performance.
Please, please, please, can other people test my non-fragile ivars patch so that we can get rid of ugly hacks like this and just not declare any ivars in the headers. I posted it months ago and have had absolutely no reports of testing yet.
David _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
