Elko Tchernev wrote: > > While changing laptops, I installed the latest Win32 > self-installing Gforth 0.6.2, and my programs promptly stopped loading, > giving file I/O errors. (Under Win XP Pro). As I've used the previous > 0.6.2 self-install with no problems, I had it on my old drive, and when > I replaced the new cygwin1.dll (1,114K, 2004-08-01) with the old one > (949K, 2003-08-30), everything was fine again. The symptom is that > INCLUDED cannot load any file that has directory specifiers in the name. > If I say S" test1.f" INCLUDED, and the file is in the current > directory, it works, but if the command is > S" /elko/work/forth/new-oof/test1.f" INCLUDED, it fails. (It fails with > both dir separators, / and \, while INCLUDE works with the DOS standard > \ separator only).
There is a change in Cygwin1.dll in how it deals with file names. Essentially, as soon as there is a "\" in the file name, it is now treated as a DOS/Windows filename, not a Unix one; the "\" may come from prepending a path component. > Is there a significant reason to use the new cygwin1.dll as opposed > to the old one? I don't see anything wrong with the old one so far, but > maybe there's some hidden issue? The old cygwin1.dll did not work correctly for W98 and WME, so there is no reason for you to switch. However, the new directory behaviour is not considered a bug by the Cygwin maintainers, and is going to stay (and you will get it with the next Gforth release). - anton --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
