In message <20090803142403.gb7...@derik>
Vincent Sanders <[email protected]> wrote:
> On Sun, Aug 02, 2009 at 12:25:59PM +0100, John Tytgat wrote:
> > In message <1249201044.20182.379.ca...@duiker>
> > John-Mark Bell <[email protected]> wrote:
> >
> > > What's wrong with calling _dom_exception_from_lwc_error() here?
> >
> > I would like to suggest to step away from using function names having
> > a leading underscore. When you want to indicate that a function name
> > is internal to a (static) library and not part of its public API, use
> > something like "dom_internal_".
> >
> > The point is that such leading underscore characters for identitiers
> > are reserved according to C(99 ?):
> > <URL:http://www.open-std.org/JTC1/SC22/wg14/www/docs/n1124.pdf>.
>
> Section 7.1.3 states:
>
> - All identifiers that begin with an underscore and either an uppercase
> letter or another underscore are always reserved for any use.
>
> - All identifiers that begin with an underscore are always reserved for
> use as identifiers with file scope in both the ordinary and tag name
> spaces.
>
> So providing we always use _[a-z]* we are using them as intended afaict
No, reserved means that using those can result in undefined behaviour
(assuming your intention is not to provoce undefined behaviour ;-).
--8<--
J.2 Undefined behavior
[...]
- "The program declares or defines a reserved identifier, other than as allowed
by 7.1.4 (7.1.3)."
--8<--
The library mentioned in 7.1.4 is the standard C library defined in that
spec, not user libraries we're designing here.
John.
--
John Tytgat
[email protected]
