bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Documentation Bug?


From: Richard Frith-Macdonald
Subject: Re: Documentation Bug?
Date: Fri, 17 Jun 2005 10:48:15 +0100

On 2005-06-17 10:22:46 +0100 Patrick McFarland <pmcfarland@downeast.net> wrote:

On Friday 17 June 2005 12:19 am, Richard Frith-Macdonald wrote:
I've fixed the programming manual ... worse than just a typo ... wrong on
memory management in a few places, with the appearance that the author was
wrong/confused in understanding what +new methods do.
I don't know how we missed it during proofreading.  It could probably do
with other people checking it too, as it's obviuously easy to miss these
things.

re: Point class example.

The consensus of #gnustep is that doing [[self allocWithZone: NSDefaultMallocZone()] init] is retarded. #gnustep also thinks implementing +new yourself instead of using NSObject's implementation is retarded. If people wanted speed they wouldn't be using +new in the first place.

Jeff Teunissen say about the example, "It's 'efficient' at great expense, doesn't fit the standard models, is excessively verbose."

Please correct Point class example in the manual.

Hey, I changed it to fix an error and (since it's a tutorial) added some more information and clarification. Certainly, you wouldn't normally re-impliment +new yourself except for performance ... but this is an example ... the original author chose to use +new and I don't see a particular reason to remove it. Going the whole way to an extremely optimised implementation would (IMO) be far too complex for the context though.

I don't want to get into debates about personal style preferences.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]