[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: dia2code objc
From: |
Bjoern Giesler |
Subject: |
Re: dia2code objc |
Date: |
Tue, 26 Mar 2002 17:04:36 +0100 |
Am Dienstag, 26. März 2002 16:55 schrieb Nicola Pero:
> ones. He will have to use hacks to access them ... at least declaring
> them manually or such ... which is enough of a guarantee that he really
> knows it's private stuff and he really thinks it's the only way for him
> to do what he needs.
IMHO, putting a notice like "you should never call these directly" in the
interface and/or documentation is plenty enough. Enforcing privacy
through any other way means that the library / component developer has to
think of every single possible use that the library / component can be
put to, later on, by the application developer. I claim that this is
impossible, and can name a couple of examples where I had to re-write
huge parts of library frameworks because I was forbidden, by the
compiler, to access certain instance variables. (Well, I didn't really
re-write them but used ugly pointer tricks, but you get my point.)
Regards,
--Björn
- Re: dia2code objc, (continued)
Re: dia2code objc, Philippe C.D. Robert, 2002/03/26
Re: dia2code objc, Nicola Pero, 2002/03/26
Re: dia2code objc,
Bjoern Giesler <=
Re: dia2code objc, Björn Gohla, 2002/03/26
RE: dia2code objc, Mondragon, Ian, 2002/03/26
RE: dia2code objc, Mondragon, Ian, 2002/03/26
RE: dia2code objc, Mondragon, Ian, 2002/03/26
RE: dia2code objc, Mondragon, Ian, 2002/03/26