Hi Christophe,

> > 4. Should the object be serializable including hidden functions?
>         [I do not understand 'serializable' ?]

By "serializable" I mean that: If I have the object (including its
private components) loaded in memory, should I be able to write the
object including its private components to a file? Or is it sufficient
if I only write the public components of the object to a file? I.e.

o: make object! [something: none]

write %filename.ext mold o

will write this object to a file. 
If I add private components to this object, and I want to write the
object to a file, should the private components be written along with
the object? Or should the object be written without the private
components, which means that when the object is subsequently loaded from
this file, it will not include the private components.

> 
> > 5. Should descendants have access to hidden functions?
>         [yes they should. Although it should be interressant to me to have a
> mean to control this: some sort of 'protected function' which is known to
> the ancestor, but not to the child objects...]

Is this "protected" function in addition to the private function? If
not, then I don't see how descendants can access the hidden function, if
this hidden function is not known to descendants.

>         That is, a private function is a function only known and accessible
> from within the context of the object. A public one is part of the public
> interface of the object and is therefore accessible from outside the object,
> by another object from exemple]

Basically, my question is, to what degree do you want to enforce this?
Is it 
a) more an organizational principle to help you as a programmer organize
your code;
b) you don't want the private functions/words to show up in the block
returned by first object, but if a non-member function absolutely wants
to, then it will 
will be able to also access hidden words ...
c) Under no circumstances must a non-member function be able to access
private components?

That's, basically what I'm asking

Take Care,

Elan
-- 
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the 
subject, without the quotes.

Reply via email to