trouble with macro`s

[Doug Gwyn]

In article <RJOHNSON.91Mar19092554 at olorin.shell.com> rjohnson at shell.com (Roy Johnson) writes:
>   But even if it "works" today, it may stop working tomorrow, as indeed
>   it must do once Sun releases a standard conforming C implementation.
>Right.  *That's* why I told him to document it.  Are you suggesting that
>he shouldn't write code that works because it isn't standard?  I suspect
>he has a job to do.

That's a short-sighted attitude.  We KNOW such code will quit "working"
some day.  That should be sufficient reason to find a better solution
that does not depend on errors in the C implementation.