🚀 go-pugleaf

Re: <iso646.h>

It seems to me that this is a reasonable solution (if I understand
it correctly).

Note that if your code does not include the <iso646.h> header file,
it does not affect you at all.  This is a key point, and differs from
the trigraph situation, where anyone can be bitten (although the
chances are pretty small), whether s/he knows about them or not.

On the other hand, if you are in an environment where some or all of
the "national" characters have been redefined, making the standard
ASCII graphics unavailable, there are now standard substitutions that
are reasonably readable (at least in English!), less ugly than
trigraphs, and that you can get used to consistently in all code.
Without this proposal, everyone affected by the problem would [do] no
doubt adopt their own macros, degrading the readability of their code.

Peter Curran
Usenet: peter.curran@canrem.com     RIME: CRS (#118)
---
 þ DeLuxeý 1.25 #12339 þ 
--
Canada Remote Systems  - Toronto, Ontario
World's Largest PCBOARD System - 416-629-7000/629-7044