Path: utzoo!attcan!utgpu!watmath!iuvax!uxc.cso.uiuc.edu!tank!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.lang.c Subject: Re: Contents of argv[0] Keywords: start-up code, argv specifications Message-ID: <19112@mimsy.UUCP> Date: 16 Aug 89 13:38:19 GMT References: <9002@attctc.Dallas.TX.US> <10743@smoke.BRL.MIL> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 15 In article <10743@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes: >... If you're going to display argv[0] (which is about the only meaningful >thing you can do with it), why not just print the whole thing. I went around with this several times myself when installing a general error-message facility in our local C library, and came up with the same answer: print the whole thing. The only bad effect is that occasionally someone will see more detail than needed. Eliding all but the `program name' part (on Unix, all but the last path component) has the bad effect that occasionally someone will miss detail that was needed (e.g., whether the error came from the new experimental version of a program or the old known-buggy version or. . .). -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris