Article View: comp.bugs.sys5
Article #770SVr3 and SVID compliance
From: David F. Carlson
Date: Mon, 18 Apr 1988 20:58
Date: Mon, 18 Apr 1988 20:58
24 lines
1271 bytes
1271 bytes
According to my reading of SVID guide documents, command line
arguments are single character, delimited by "-" and followed
by a space and perhaps an optional string. Many commands of SVr3 still
do not permit the (non-optional) space after the key flag. And
one command in particular (/lib/cpp) destroys the input file
if SVID compliance is assumed:
Demonstrate: (Under SVr3.0 as sold by Microport)
1) /lib/cpp -I../inc main.c # command behaves as expected
2) /lib/cpp -I ../inc main.c # command fails miserably
Note space ^
(2) will assume that ../inc is the input file (even though it is a directory)
and will copy the directory into the presumed output file (which is actually
the intended *input* file!)
--
David F. Carlson, Micropen, Inc.
...!{ames|harvard|rutgers|topaz|...}!rochester!ur-valhalla!micropen!dave
"The faster I go, the behinder I get." --Lewis Carroll
Technical Details
Message-ID:
<460@micropen>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!uunet!husc6!bbn!rochester!ur-tut!ur-valhalla!micropen!daveShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!husc6!bbn!rochester!ur-tut!ur-valhalla!micropen!dave From: dave@micropen (David F. Carlson) Newsgroups: comp.bugs.sys5 Subject: SVr3 and SVID compliance Message-ID: <460@micropen> Date: 18 Apr 88 20:58:19 GMT Organization: Micropen Dirent Writing Systems, Pittsford, NY Lines: 24 Keywords: argument lists SVID