Print

Print


>Ah, OK, this clarifies it. Sure, no nested types. Makes sense.
>
>In that case, since only a single data element can be declared in
>the private part, and none at all in the public part, the use of
>"private" is really just syntactic sugar.

We can declare as many objects as necessary; not just one.

>It's not a real private part in the sense of packages. It does
>serve as a useful delimiter for the compiler, I guess.

No, it really is private in the same sense as packages and tasks. For
example, we can declare private entries and protected subprograms,
primarily for the sake of requeue.


-- pat

Pat Rogers
[log in to unmask]
http://www.neosoft.com/~progers
(281)648-3165