Thread View: comp.bugs.sys5
2 messages
2 total messages
Started by David F. Carlson
Mon, 18 Apr 1988 20:58
SVr3 and SVID compliance
Author: 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
Re: SVr3 and SVID compliance
Author: Anonymous Author
Date: Sat, 23 Apr 1988 01:35
Date: Sat, 23 Apr 1988 01:35
3 lines
355 bytes
355 bytes
zilch .signature
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads