Re: My not-quite obsolete namespace parser

new topic     » goto parent     » topic index » view thread      » older message » newer message

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

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu