OpenEuphoria

RE: My not-quite obsolete namespace parser

• Posted by Chris Bensler <bensler at mail.com> May 14, 2002
• 352 views

Regardless of whether it's an intended 'feature', or a bug, it's a 
problem.

What is the reason that eu DOS/WIN can't use '/' just the same as '\'?

I prefer to use '/' so I don't have to change my code when I take it to 
linux.
It seems silly to me to force developers to use the DOS convention, 
especially considering '\' is already used in eu as the switch char.
If ANYTHING, it should only allow '/', to maintain a cross platform 
standard.


Chris


Robert Craig wrote:
> Derek Parnell writes:
> > In file 'a.e' enter these three lines...
> >
> >  global myval
> >  myval = 1
> >  ? 1
> >
> > In the file 'b.ex' enter these two lines...
> >
> >  include ./a.e
> >  include a.e
> >
> > Now execute b.ex. When I do this I get ...
> >
> > 1
> > 1
> 
> If I correct "global myval" to "global integer myval",
> and I correct "./a.e" to ".\a.e", then
> it correctly prints a single "1" on DOS or Windows.
> 
> Or if I use "./a.e" on Linux or FreeBSD it also
> correctly prints a single "1".
> 
> Euphoria assumes "\" in file paths on DOS and Windows,
> and "/" and Linux and FreeBSD. If you have something else
> it just passes it through to the O/S. It looks like DOS and Windows
> will accept "/" in some cases (but not all).
> Linux and FreeBSD never accept "\".
> 
> Regards,
>    Rob Craig
>    Rapid Deployment Software
>    http://www.RapidEuphoria.com
> 
>