🚀 go-pugleaf

In article <3vqrg1$bem@caip.rutgers.edu> halasz@caip.rutgers.edu writes:
>In article <danpop.807407394@rscernix>, Dan.Pop@mail.cern.ch (Dan Pop) writes
>! It's all your fault.  Here's the relevant part of the standard:
>! 
>!     4.1.3 Errors <errno.h>
>! 
>!     The header <errno.h> defines several macros, all relating to the
>!     reporting of error conditions.
>! 
>!        The macros are 
>!            ^^^^^^
>!            EDOM
>!            ERANGE
>! 
>!     which expand to distinct nonzero integral constant expressions; and 
>! 
>!            errno
>! 
>!     which expands to a modifiable lvalue that has type int...
>!           ^^^^^^^

>The standard looks wrong to me ....
>full of traps for the innocent.

The innocent would not use identifiers defined by the standard for their own 
purposes even if the standard allowed them too.

Name space management is _extremely_ important (IMHO) and is one of VMS's 
strengths. Perhaps the people who wrote the original 'errno' member had 
been lulled by VMS into thinking that they could do no wrong (no $ => OK)

I suggest a global subsititute of '.errno' and '->errno' to a new name as a 
first pass.  These two strings won't show up very often (if at all) in your 
programs other than in the places that you want to change them.

Claude.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 vv    vv       David Claude Brown
 ||----||  *    brown@falam.ch
 ||     | /
 /\------/
(oo)
(~~)