On Wed, Mar 12, 2003 at 11:42:25PM +0000, Tom Payne wrote:
What you should do:
Either:
1) Declare everything public, and comments to the class declaration saying
"don't call this function" or "for internal use only" or words to that
effect. Data hiding isn't needed when you trust the people using your code
:-)
where's the advantage over a structure with pointer to functions (except
inheritance, which could be emulated, no I don't like vpointer tables ;))
I recommend option 1. As Ion is currently being developed just make
everything public and worry about private/protected when things have
stabilised.
I've access protection is not needed it should never get into ion. As
i've stated before it is possible to create object oriented programms
without using oo languages.
Another question is how much the performance disadvantage of those
access checks would be, but as there's at least one widly known window
manager ((black|flux|open)box) family out there this can't be _that_
problem.
Regards,
Tom
Andreas
--
...the moral of the story might be to never engage in copyright
violation unless you have an unstable friend with several thousand
nuclear warheads lying about. --Fox news, on the Sklyarov case
