Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!tektronix!sequent!mntgfx!rengland
From: rengland@mntgfx.mentor.com (Richard England)
Newsgroups: comp.unix.wizards
Subject: Re: To . or not to .
Message-ID: <1987Nov13.082905.186@mntgfx.mentor.com>
Date: Fri, 13-Nov-87 11:29:01 EST
Article-I.D.: mntgfx.1987Nov13.082905.186
Posted: Fri Nov 13 11:29:01 1987
Date-Received: Sun, 15-Nov-87 11:15:15 EST
References: <9363@tekecs.TEK.COM<
Organization: Mentor Graphics Corporation, Beaverton Oregon
Lines: 41

in article <9363@tekecs.TEK.COM<, snoopy@doghouse.gwd.tek.com (Snoopy) says:
< 
< In article <972@tut.cis.ohio-state.edu> lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani) writes:
< 
<>SVR2 (and any AT&T Unix system I'm familiar with) lets you use
<>multiple /.
<>
<>	//a is the same as /a
<>	a//b is the same as a/b
<>
<>This nice thing about doing it this way is that you can be a little
<>sloppy in your program and it will still work.  I admit it I'm lazy!
<>And what is the harm anyway?
< 
< The harm is that this is not portable.  With UTek's DFS, //a refers to the
< root directory on a machine called 'a'.  I've seen articles indicating
< that Apollo's multi-machine file system (whatever they call their version)
< uses the same syntax.  (Is anyone familiar with Apollo out there?)
< 
< Sloppy programming is not a good idea.
< 
< Snoopy
< tektronix!doghouse.gwd!snoopy
< snoopy@doghouse.gwd.tek.com





//a on an Apollo Domain network specifies a node name.  Hence //a is 
a no-no.  Both BSD and SYSTEM V Unix on a Domain network will recognize
the node name so beware.  Why not just stick to the published norms and 
be safe?



-- 
 ----------------------------------------------------------------------------
 Rich England                  | "...Cock o' the North?  Ach! Yon's a cheesey
 rengland@mntgfx.MENTOR.COM    |tune.  Weel no be playin' thaat tune!"
 ...!tektronix!sequent!mntgfx  |     Alec Guiness, "Tunes of Glory"