Re: child packages and nested packages

[okellogg@freenet.de (Oliver Kellogg)]

Nevermind, problem solved.

FYI:
Turned out that during parsing, one should never directly assign a
synthesized node from already constructed nodes.
Reason: The constructed nodes have additional fields set that make the
compiler assume the new node has already been semantically analyzed.
Instead, use New_Node (or the Nmake.Make_ methods) in combination with
Chars and other accessors to copy the individual node fields.

I'll refrain from attaching the corrected diff, mail me if you
want it.

Next, I'll look at how to make visible to the child the nested parent's
private part.