OpenEuphoria

RE: another look at namespaces

• Posted by Matt Lewis <matthewwalkerlewis at yahoo.com> Jul 11, 2003
• 614 views

> From: Pete Lomax [mailto:petelomax at blueyonder.co.uk]
> 
> >> From: Derek Parnell [mailto:ddparnell at bigpond.com]
> >
> >> Please find a new term other than 'include path' because it 
> >> took me a few readings of this to realize that your were NOT 
> >> talking about EUINC environment symbol or similar.
> >
> >Yes, I've been uncomfortable with that, too, just haven't 
> come up with
> >anything yet.
> >
> How about "local include statements"?
> 

I don't think that's quite right.  Local include statements says to me that
you're talking about include statements in one file.  But I'm really talking
about the include statements within the file, plus the include statements
within the included files, etc.  Perhaps 'include tree' would be better.  So
for alice/bob/chris/diane/erin:

+-alice <empty>
|
+-bob
|  +------alice
|
+-chris <empty>
|
+-diane
|  +----chris
|
+erin
  |----diane
  |     +---chris
  |
  +----bob
        +-----alice

In fact, the way it's stored is:

erin: {bob, diane}
bob: {alice}
alice: <empty>
diane: chris
chris: <empty>

The content within {} are a linked list, each of which is a structure
containing the respective index in the array and a pointer to the next item
in the list (if any).  So it's pretty easy to determine if one file is in
another's include tree.

Matt Lewis