Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!ucbvax!hplabs!hpfcso!hpfelg!koren From: koren@hpfelg.HP.COM (Steve Koren) Newsgroups: comp.sys.amiga.tech Subject: Re: Bug in Open(), and problem w/SKsh Message-ID: <13920019@hpfelg.HP.COM> Date: 27 Nov 89 04:34:32 GMT References: Organization: HP Elec. Design Div. -FtCollins Lines: 27 >Presumably, none of these programs check to see what kind of "object" they're >being asked to edit/touch/whatever ahead of time :-( They do fail (usually) >when they attempt to get a write-lock from Open() to write the modified "file" >contents, but apparently Open() returns a valid (?) write-lock if the file is >really an empty directory! [This is my speculation on what's going on.] I'll look into it and fix it in the next version. It will be easy to fix. >However, there is another bug in SKsh that I found that resulted in the "Ye >Olde read/write error requester" popping up. Seems that SKsh (v1.2) lets you >cd into any object (if that makes any sense), be it directory, file, 0-length, >or not. And whilst "inside" a file (wherever that is), uglyness may befall ..... > you don't "cd" into files (how *are* you managing this trick, Steve ?). Well, I just check the return code from the chdir() call. I don't remember right now if I use Lattice's or the AmigaDos one. Anyhow, if the chdir() fails then I report an error. Maybe chdir() isn't failing when it should be. I guess I can fix it by checking the object type explicitly. > [ksh type gratitude sufff] Finally! Thank you Steve!!! You bet. This seemed like a void in the Amiga software world begging to be filled. - steve