Xref: utzoo comp.std.c:2190 comp.lang.c:24016 Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.std.c,comp.lang.c Subject: Re: ansi c and directories Message-ID: <7108@ficc.uu.net> Date: 26 Nov 89 18:07:40 GMT References: <13295@s.ms.uky.edu> <20881@mimsy.umd.edu> <7100@ficc.uu.net> <17359@rpp386.cactus.org> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 24 In article <17359@rpp386.cactus.org> jfh@rpp386.cactus.org (John F. Haugh II) writes: > i've worked on enough strange o/s's that i can safely say the number of > operations common to all hosted implementations directories is the > empty set. The only operating systems I know of that wouldn't support "Open current directory", "Next file in current directory", and "Close current directory" are either obsolete (one person brought up CDC NOS) or are required to hide file names for security reasons. Given your security background I would expect such operating systems would loom pretty large, of course. [ long description of weird file name conventions ] Yes, but that's not relevant. Nobody said that the standard had to specify what a file name looks like. All these apply equally to "fopen", etc... > hell, my hp-41cv didn't even have a directory, i think. Didn't have files, either. And probably can't run C. -- `-_-' Peter da Silva . 'U` -------------- +1 713 274 5180. "The basic notion underlying USENET is the flame." -- Chuq Von Rospach, chuq@Apple.COM