Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!mailrus!accuvax.nwu.edu!tank!eecae!cps3xx!usenet From: usenet@cps3xx.UUCP (Usenet file owner) Newsgroups: comp.lang.c Subject: Re: Contents of argv[0] Message-ID: <4200@cps3xx.UUCP> Date: 17 Aug 89 14:47:22 GMT References: <19112@mimsy.UUCP> Organization: Engineering, Michigan State U., E. Lansing MI Lines: 18 in article <19112@mimsy.UUCP>, chris@mimsy.UUCP (Chris Torek) says: > Keywords: start-up code, argv specifications > 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. ^ +--- Counterpoint: ex, vi, and view are all the same binary. They look at argv[0] to enough which one to do. Also, compress and uncompress do the same thing. John H. Lawitzke UUCP: Work: ...uunet!frith!dale1!jhl Dale Computer Corp., R&D Home: ...uunet!frith!dale1!ipecac!jhl 2367 Science Parkway Internet: jhl@frith.egr.msu.edu Okemos, MI, 48864 [35.8.8.108]