RE: Section 4.1 clarifications

["Michael Krueger" <michael.krueger@windriver.com>]

> Getting really picky -

Getting picky in the right context is a good thing.  As an implementer, I'm
all for tightening up the spec to reduce the scope of valid input I have to
handle!  ;-)

> Shouldn't a hex constant be:
> hex constant:      unsigned hexadecimal constant described by
>                    regular expression "0[xX][0-9a-fA-F]+"

Good catch.  This was a cut 'n' paste error on my part.

> Also, why is "binary item" not "binary constant"?

I was trying to preserve terms that were already in use in the spec.
"Binary constant" would be fine with me, as long as it were to replace all
current instances of "binary item."  I don't care what words make up the
terms, as long as they're defined clearly and used consistently throughout
the spec!

Michael

--
Michael J. Krueger              mailto:michael.krueger@windriver.com
Wind River Networks                         http://www.windriver.com
500 Wind River Way                               phone: 510-749-2130
Alameda, CA  94501                                 fax: 510-749-2010