[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zh5ixcn9.fsf@oldenburg2.str.redhat.com>
Date: Tue, 22 Sep 2020 13:40:42 +0200
From: Florian Weimer <fweimer@...hat.com>
To: Ville Voutilainen <ville.voutilainen@...il.com>
Cc: Jonathan Wakely <jwakely@...hat.com>, Alejandro Colomar
<colomar.6.4.3@...il.com>, gcc@....gnu.org, "libstdc++"
<libstdc++@....gnu.org>, Libc-alpha <libc-alpha@...rceware.org>,
libc-coord@...ts.openwall.com
Subject: Re: Expose 'array_length()' macro in <sys/param.h>
* Ville Voutilainen:
> Why should this be array_length and not __array_length? This is a
> vendor extension, so it should use
> a name that is reserved for such?
In general, we use __ for glibc internals that are not intended for
direct access by users. In some cases, we have non-__ identifiers that
are redirected to these __ identifiers.
In some cases it may be beneficial to expose vendor extensions under __
names, so that they can be used in strict standard modes, but we are
quite far away from that for C++ at least.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
