Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde!uunet!lll-winken!brutus.cs.uiuc.edu!wuarchive!texbell!nuchat!sugar!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.lang.c Subject: Re: ansi c and directories Message-ID: <7202@ficc.uu.net> Date: 5 Dec 89 14:15:42 GMT References: <225800244@uxe.cso.uiuc.edu> <3332@cbnewsd.ATT.COM> <7127@ficc.uu.net> <11707@smoke.BRL.MIL> <7156@ficc.uu.net> <1292@uwm.edu> <7193@ficc.uu.net> <11738@smoke.BRL.MIL> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 26 In article <11738@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes: > In article <7193@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes: > >In any system for which files have names, there is at least one directory. > Not necessarily one that could be opened by name. Doesn't have to. Surely you can see a way around that. Have a default that's used when you specify a file name of NULL. > >Thus a routine that returns the names of files in at least the current > >directory is more generally portable than system(). > The concept of "current directory" is also not portable. Sure it is. It's where the system looks up the file names you give it. > >And, as you pointed out, system() is in the standard. > system() was in the library Base Document; the dirent stuff wasn't. Pity. -- `-_-' Peter da Silva. +1 713 274 5180. . 'U` Also or . "If you want PL/I, you know where to find it." -- Dennis