peraino@gmu90x.gmu.edu (peraino) (11/14/89)
>From crwth@kuling.UUCP Mon Nov 13 08:14:03 1989 >Very nice, but isn't it a little bit awkward to traverse the >whole path, just to go one step upwards? Why not do it like this? . . . . >It won't work if the current directory has a child with the same name >as the parent to the current directory or if the current directory is >the home directory (has no parent), but that doesn't matter in my opinion. In my opinion, it DOES matter. A function that isn't robust enough to handle that simple case isn't a very good function. MY version evaluates the whole path. I have had several directories in the past that would have fallen prey to the situation that you describe above. It is not that uncommon. I may want to design an alarm package (real life situation here) and I will call the directory ALARM. Now during the design, I will probably call the main module ALARM. Guess what happens when I use your version of UP? The user shouldn't have to worry about avoiding this situation, since I believe it can be a very common problem. ----------------------------------------------------------------------------- Bob Peraino UUCP : uunet!pyrdc!gmu90x!peraino George Mason University INTERNET: peraino@gmuvax.gmu.edu UCIS, Thompson Hall, rm 2 <- BITNET : peraino@gmuvax 4400 University Drive \ PHONE : (703)-323-2549 Fairfax, VA 22030 \- Yeah, they put us in the basement, too. -----------------------------------------------------------------------------