access()

[Doug Gwyn]

In article <3281 at ficc.uu.net> peter at 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.