Dennis Ruffer wrote: > > You may be close: > > $ ./gforth > GForth 0.5.9-20030201, Copyright (C) 1995-2003 Free Software Foundation, > Inc. > GForth comes with ABSOLUTELY NO WARRANTY; for details type `license' > Type `bye' to exit > s" /usr/local/share/gforth/0.5.9-20030201\kernl32l.fi" r/o open-file ok > .s <2> 0 -514 ok > > Now, what's the fix and why did 0.5.0 work fine?
My guess is that the open() in the cygwin used for the 0.5.0 port did recognize both "/" and "\" as directory separators. E.g., on the Cygwin where I have done some testing I get: s" /home/anton/gforth-0.5.9-20030127\README" r/o open-file ok .s <2> 168035552 0 ok $ uname -r 1.3.18(0.69/3/2) One fix is to use such a Cygwin version; however, if this behaviour is not a bug, then this fix has no future. Another fix is to delete the cygwin special-casing in configure.in. > Maybe it's not recognizing > that this is in fact a Unix derivative? Actually we are special-casing Cygwin to make Gforth behave like a good Windows application (e.g., CRLF newlines). I guess most Gforth users on Windows don't view Cygwin as a Unix and expect Windows-like behaviour. - anton --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
