Article View: comp.os.msdos.programmer
Article #2895Re: Command line length (was: Can std-io be a *binary* file?)
From: Jim Miller
Date: Fri, 02 Nov 1990 01:43
Date: Fri, 02 Nov 1990 01:43
22 lines
1306 bytes
1306 bytes
>As to the idea of the shell performing filename expansion: what a bad design >that is. Programs should see what the user types, not what the >shell transforms it into. > >Duncan Murdoch >---------- That statement obviously is the opinion of the author and has nothing to do with reality -- unlike my statements :-) So you think every programmer should do their own expansions? And everyone can be different except those who don't do it at all? If one wants it literally, "make it literal". I've got better things to do than fight inconsistent interfaces and waste time coding something that should be done for me. jim miller jamiller@hpmpeb7.cup.hp.com (a.k.a James A. Miller; Jim the JAM; stupid; @!?$$!; ... ) Anything I say will be used against me ... But my company doesn't know or approve or condone anything of mine here.
Technical Details
Message-ID:
<51040001@hpcupt1.cup.hp.com>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpda!hpcupt1!jamillerReferences:
<1990Nov1.142426.19559@maytag.waterloo.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpda!hpcupt1!jamiller From: jamiller@hpcupt1.cup.hp.com (Jim Miller) Newsgroups: comp.os.msdos.programmer Subject: Re: Command line length (was: Can std-io be a *binary* file?) Message-ID: <51040001@hpcupt1.cup.hp.com> Date: 2 Nov 90 01:43:19 GMT References: <1990Nov1.142426.19559@maytag.waterloo.edu> Organization: Hewlett Packard, Cupertino Lines: 22