Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!pikes!aspen.craycos.com!ewv
From: ewv@craycos.com (Eric Varsanyi)
Newsgroups: comp.unix.programmer
Subject: Re: Why use pwd(1) for getpwd(3C)? (Re: Why use find?)
Message-ID: <1990Oct12.200410.1965@craycos.com>
Date: 12 Oct 90 20:04:10 GMT
References: <1990Oct9.122813.1329@cbnews.att.com> <23012:Oct1019:12:2790@kramden.acf.nyu.edu> <1990Oct11.012643.11274@diku.dk>
Organization: Cray Computer Corporation
Lines: 13

In article <1990Oct11.012643.11274@diku.dk> kimcm@diku.dk (Kim Christian Madsen) writes:
>That's maybe the indirect reason, the rest is because of sloppy AT&T
>programmers, that figured that there was no reason to copy code from
>pwd(1) into the getpwd(3C) routine. SYSVR4 is supposed to eliminate this
>idiotic behaviour of getpwd(3C), and I pray that AT&T have learned from
>the negative response they have got, and do not try this path again.
>

	Getcwd.c in SVR4 does not use popen/system. It does what you
might expect (walks up the tree using '.' and '..').

-- 
-Eric Varsanyi (ewv@craycos.com)        Cray Computer Corporation