1. Watcom compile error for certain file names
- Posted by Juergen Luethje <j.lue at gmx.de> Jul 05, 2006
- 684 views
Hello Rob, it looks as if there is a bug in the Eu2C translator 2.5, or in the Open Watcom 1.3 C compiler. Please note that the problem doesn't seem to depend on the content of the Euphoria source file, but only on its name. The following code compiles fine: ----------------------------[ test.ex ]------------------------------- puts(1, "Hello world!\n\nPress Enter ...") if getc(0) then end if ---------------------------------------------------------------------- when using ec -wat ... or ecw -wat ... But after renaming the file e.g. to "test(1).ex", both commands can't be used anymore for compiling. I did not encounter this problem using DJGPP on DOS or the Borland compiler on Windows (LCC not tested, and nothing tested on Linux/FreeBSD). It would be nice if this problem could be fixed. Regards, Juergen -- Please excuse my flawed English. My native language is Euphoria.
2. Re: Watcom compile error for certain file names
- Posted by Bernie Ryan <xotron at bluefrog.com> Jul 05, 2006
- 635 views
Juergen Luethje wrote: > > Hello Rob, > > it looks as if there is a bug in the Eu2C translator 2.5, or in the Open > Watcom 1.3 C compiler. Please note that the problem doesn't seem to > depend on the content of the Euphoria source file, but only on its name. > > The following code compiles fine: > > ----------------------------[ test.ex ]------------------------------- > puts(1, "Hello world!\n\nPress Enter ...") > if getc(0) then end if > ---------------------------------------------------------------------- > > when using > ec -wat ... > or > ecw -wat ... > > But after renaming the file e.g. to "test(1).ex", both commands can't be > used anymore for compiling. > > I did not encounter this problem using DJGPP on DOS or the Borland > compiler on Windows (LCC not tested, and nothing tested on Linux/FreeBSD). > It would be nice if this problem could be fixed. > Juergen: Ephoria translator probably thinks "test(1).ex" is a function/procedure name called test(). Bernie My files in archive: WMOTOR, XMOTOR, W32ENGIN, MIXEDLIB, EU_ENGIN, WIN32ERU, WIN32API Can be downloaded here: http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan
3. Re: Watcom compile error for certain file names
- Posted by Robert Craig <rds at RapidEuphoria.com> Jul 05, 2006
- 622 views
- Last edited Jul 06, 2006
Juergen Luethje wrote: > it looks as if there is a bug in the Eu2C translator 2.5, or in the Open > Watcom 1.3 C compiler. Please note that the problem doesn't seem to > depend on the content of the Euphoria source file, but only on its name. > > The following code compiles fine: > > ----------------------------[ test.ex ]------------------------------- > puts(1, "Hello world!\n\nPress Enter ...") > if getc(0) then end if > ---------------------------------------------------------------------- > > when using > ec -wat ... > or > ecw -wat ... > > But after renaming the file e.g. to "test(1).ex", both commands can't be > used anymore for compiling. > > I did not encounter this problem using DJGPP on DOS or the Borland > compiler on Windows (LCC not tested, and nothing tested on Linux/FreeBSD). > It would be nice if this problem could be fixed. It looks like the Watcom linker doesn't like filenames with brackets in them. I'll make a note of this, but I have a lot of other higher priority stuff to get moving on. Thanks, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com