Path: utzoo!attcan!uunet!tank!mimsy!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: access()
Message-ID: <9779@smoke.BRL.MIL>
Date: 3 Mar 89 11:53:41 GMT
References: <LFK.89Feb8170836@mbio.med.upenn.edu> <979@auspex.UUCP> <1040@auspex.UUCP> <3281@ficc.uu.net>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Distribution: comp
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <3281@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>Ah, but AT&T systems have no problem with "//" or "///" or "/////", ...

IEEE 1003.1 requires that consecutive slashes be allowed and in effect
be interpreted as a single slash.  (Thus OpenNet's convention would not
be POSIX-compliant.)

The only reason I can think of for an application to merge adjacent
slashes is to compensate for sloppy programming.