Am 16.07.2009 um 12:24 schrieb David Chisnall:
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.
Maybe it's not clear to everybody what benefits your patch
introduces. So maybe it would be a good idea to give a short
enumeration of all the gains to the broader public (I know you're
good at writing technical articles since I read quite a few off
them :-)).
David
thanks,
Lars
_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev