Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!hc!lanl!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: access()
Message-ID: <9641@smoke.BRL.MIL>
Date: 10 Feb 89 14:14:21 GMT
References: <LFK.89Feb8170836@mbio.med.upenn.edu> <979@auspex.UUCP> <5615@bsu-cs.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Distribution: comp
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <5615@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
>Hmmm...as I understand it, this disallows pathnames of the form
>"//filename" and is ambiguous about pathnames of the form
>"filename//filename".

The first form has special meaning in some network-extended implementations.

A null path component is not accepted by UNIX System V, as I recall.

>This is not very UNIX-like.

Hey, these days UNIX isn't very UNIX-like.