1. Re: Include System (was Standardized Euphoria)
Chris Bensler wrote:
> I mean if the programmer only wants to include bob.e eventhough bob/bob.e
> exists also.
>
> > >
> > > What if I have bob\bob.e already and I want to move the file into the
> > > project folder?
> > Erm, I don't follow you. What problem are you expecting here?
>
> I mean if the project file has
> include bob\bob.e
>
> and you then move bob\bob.e to bob.e
> does your solution help?
No. And it should not[1].
If you have main.e and bob.e in myapp/ where myapp/main.e is:
include chris/chris.e
and myapp/chris/chris.e is:
include bob.e
and there is no myapp/chris/bob.e, then yes, it will include myapp/bob.e
Totally standard behaviour imo.
If there is also a myapp/bob/bob.e then obviously it will not be loaded.
If there is the above but no myapp/bob.e and you have not previously included
bob/bob.e, it will not perform a nested dir() scan looking
for it, it will just tell you it cannot find it.
If myapp/chris/chris.e is instead:
include bob/bob.e
and there is no myapp/bob/bob.e or myapp/chris/bob/bob.e then it will not
be happy with myapp/bob.e (since the partial directory does not match) and tell
you it cannot find it[1].
Otoh if one of those does exist (obviously myapp/chris/bob/bob.e would be
included in preference) then to also include myapp/bob.e then that's the
statement you need (or ..\bob.e), ditto myapp/bob/bob.e.
Regards,
Pete
