🚀 go-pugleaf

In article <May.23.14.52.22.1989.3122@pilot.njin.net> limonce@pilot.njin.net (Tom Limoncelli) writes:
>In article <1410019@hpcvca.CV.HP.COM> stan@hpcvca.CV.HP.COM (Stan Gibbs) writes:
>>         USHORT chip imagepts[] ...

>To be 100% ANSI conformant (that is, when ANSI gets officially adopted
>and products can really be ANSI conformant) wouldn't they NOT be
>allowed to add a keyword like "chip"?  Shouldn't it be "_chip" to
>conform to the namespace requirements?  (venders can use all the
>symbols that begin with "_")

In a word, yes.  They actually support 2 versions, "chip" and "__chip".
The "__" version is "intended to allow for an ANSI conforming program,
while we offer the non-ANSI version for more readable code and some
compatibility with MSDOS based products" (from the 5.0 User's Guide,
quoted without permission).  In think they should not allow "chip", but at
least they are aware of the issue, and most of their extensions do begin
with "__".

-Dan Riley (riley@tcgould.tn.cornell.edu, cornell!batcomputer!riley)
-Wilson Lab, Cornell U.