[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bogus retain via NSEnumerator
From: |
David Stes |
Subject: |
Re: bogus retain via NSEnumerator |
Date: |
Sat, 24 Apr 2004 14:14:49 GMT |
User-agent: |
tin/1.5.8-20010221 ("Blue Water") (UNIX) (Linux/2.4.18 (i686)) |
In comp.lang.objective-c John C. Randolph <jcr@nospam.idiom.com> wrote:
>>
>> If you ever wrote a piece of real software, you'd know that portability is
>> important in the real world; regardless of what you may wish.
>
> I'm well aware of the importance of portability. That's why I use GCC.
I'm afraid portability is more than just that, Mr. Apple employee.
Instead of boasting that you follow the rules of this silly autorelease memory
management, you'd better start to do some intellectual activity such as
*designing* a memory management instead of just following rules like a slave.
The creative activity of *designing* rules is all about avoid major mistakes
like the autorelease pool memory management: object-oriented design is not
about placing the responsibility for such things as memory management on the
user, it is about *hiding* complexity in modular software units.
- Re: bogus retain via NSEnumerator, (continued)
- Re: bogus retain via NSEnumerator, David Stes, 2004/04/21
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/22
- Re: bogus retain via NSEnumerator, Pete French, 2004/04/22
- Re: bogus retain via NSEnumerator, David Stes, 2004/04/22
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/23
- Re: bogus retain via NSEnumerator, David Stes, 2004/04/23
- [stes'sism] Re: bogus retain via NSEnumerator, Helge Hess, 2004/04/23
- Re: [stes'sism] Re: bogus retain via NSEnumerator, Greg Parker, 2004/04/23
- Re: bogus retain via NSEnumerator, Markus Hitter, 2004/04/23
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/23
- Re: bogus retain via NSEnumerator,
David Stes <=
- Re: bogus retain via NSEnumerator, Gregory John Casamento, 2004/04/24