1. Re: Include System (was Standardized Euphoria)
For Mr Burch, I'll add:
>
> No. And it should not[1].
>
> If you have main.e and bob.e in myapp/ where myapp/main.e is:
> }}}
<eucode>
> include chris/chris.e
> </eucode>
{{{
> and myapp/chris/chris.e is:
> }}}
<eucode>
> include bob.e
> </eucode>
{{{
> and there is no myapp/chris/bob.e, then yes, it will include myapp/bob.e
[a]
> Totally standard behaviour imo.
>
> If there is also a myapp/bob/bob.e then obviously it will not be loaded.
Totally standard behaviour.
> 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.
Totally standard behaviour.
>
> If myapp/chris/chris.e is instead:
> }}}
<eucode>
> include bob/bob.e
> </eucode>
{{{
> and there is no myapp/bob/bob.e or myapp/chris/bob/bob.e then it will not
[b]
> be happy with myapp/bob.e (since the partial directory does not match) and
> tell you it cannot find it[1].
Totally standard behaviour.
>
> 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.
[c]
>
> Regards,
> Pete
By "Totally standard behaviour" I mean that is what 2.3, 2.4, 2.5, 3.0.0,
Chris Bensler's 3.0.1, and Positive will ALL do given the conditions specified,
though 3.0.1 and Positive introduce [contentious] enhancements when the
conditions at [a], [b], and [c] are other. In addition [c] partly applies to
3.0.0 as well as several cases not explicitly mentioned.
Regards,
Pete
