Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!crdgw1!sungod!davidsen From: davidsen@sungod.crd.ge.com (ody) Newsgroups: comp.lang.c Subject: Re: Contents of argv[0] Keywords: start-up code, argv specifications Message-ID: <1767@crdgw1.crd.ge.com> Date: 18 Aug 89 21:29:28 GMT References: <9002@attctc.Dallas.TX.US> <1681@crdgw1.crd.ge.com> <1705@crdgw1.crd.ge.com> <5722@ficc.uu.net> Sender: news@crdgw1.crd.ge.com Reply-To: davidsen@crdos1.UUCP (bill davidsen) Organization: General Electric Corp. R&D, Schenectady, NY Lines: 25 In article <5722@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes: | struct filename { | char *machine; | char *volume; | char *project; | char *user; | char *path[MAXPATH]; | char *filename; | char *extension; | char *version; | }; [ ... ] | Any elements I'm missing? Well, at least device... the C:foo in MS-DOS and the DRC0:file in VMS all specify physical devices (which might be mapped in DOS, yes I know). No one can come up with a struct containing everything which might be in a path someday. All that was needed by the original poster was a way to find out the "filename" as understood by the local filesystem. bill davidsen (davidsen@crdos1.crd.GE.COM) {uunet | philabs}!crdgw1!crdos1!davidsen "Stupidity, like virtue, is its own reward" -me