SVr3 and SVID compliance

[David F. Carlson]

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