OpenEuphoria

RE: include statement bugs

• Posted by Derek Parnell <ddparnell at bigpond.com> Oct 17, 2004
• 579 views

Chris Bensler wrote:
> 
> > It's documented that Euphoria ignores the second and subsequent includes
> > of the same file name (although the directory paths could be different).
> > I've further clarified the docs about this (just now).
> > 
> 
> Perhaps <u>I</u> didn't clarify well enough.
> Don't you think, that just MAYBE, out of the thousands of euphoria 
> source files I have, that 2 of them share the same file name, although 
> the contents are DIFFEREENT!!!
> 
> The examples I gave happen to be identical, because they are minimal 
> examples.
> 
> Explain your logic for such a rediculous enforcement.

I suspect Robert was too literal. He was saying that version 2.4 behaves
this way. He did not mention v2.5 and beyond. I have asked this question
of Robert some time again and he has assured me that v2.5 will have
this and related issues corrected in 2.5.

For example:

   include .\inc1.e
   include inc1.e

are two 'different' files in 2.4 but the same file in 2.5.

> 
> > >     Using \ is apparently supposed to be the expected behaviour.
> > >     The fact that / works at all is considered a bug.
> > 
> > In 2.5, forward slash and backslash are equally supported by
> > Euphoria on DOS/Windows. Only forward slash will be supported
> > on Linux/FreeBSD. This is in keeping with what the underlying 
> > operating systems support.
> >  
> 
> That's just plain STUPID. Isn't euphoria cross platform!!!?
> I should be able to use include lib\foo.e or lib/foo.e on any platform.

It turns out that this is not so stupid after all. That's because the 
'\' character is a valid file name character in Unix-land.

Try doing this in a linux or unix...


  echo hello >my\funny\file\name


-- 
Derek Parnell
Melbourne, Australia