🚀 go-pugleaf

In <4jaeq4$9ig@golem.phys.ndsu.NoDak.edu> mooney@golem.phys.ndsu.NoDak.edu (Timothy Mooney) writes:

>In article <root.827268746@rscernix>, Dan Pop <danpop@mail.cern.ch> wrote:
>>In <4ikptb$er8@golem.phys.ndsu.NoDak.edu> mooney@golem.phys.ndsu.NoDak.edu (Timothy Mooney) writes:
>>
>>>DEC's cc for Digital Unix 3.2 has a -std option, and the man page does
>>>mention the ISO standard.
>>
>>Does it?  Not as far as I can see on my Digital Unix 3.2 box:
>
>You're not looking in the right spot (this is 3.2c):
>
>$uname -s -r
>OSF1 V3.2
>$man cc | grep -i iso
>  _ANSI_C_SOURCE   ISO C and ANSI C
>  standard.  For strict ISO C and ANSI C conformance, the compiler command
>
>Both references are earlier than the section on the arguments and their
>meanings.

Let's see:

ues5:~/tmp 20> uname -s -r
OSF1 V3.2
ues5:~/tmp 21> man cc | grep -i iso
ues5:~/tmp 22> 

Not all 3.2's are born equal :-)  (mine is 3.2a)

But I find the 3.2c man page confusing, because it talks about ISO C
and ANSI C as if they were two different standards and not two different
names for one and the same thing.

Dan
--
Dan Pop
CERN, CN Division
Email: danpop@mail.cern.ch 
Mail:  CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland