From: Carl Worth <cworth@cworth.org>
To: djcb@djcbsoftware.nl, Olly Betts <olly@survex.com>
In-Reply-To: <87pr5bw383.wl%djcb@djcbsoftware.nl>
References: <4B4ED7E8.20501@exys.org> <878wc0623y.fsf@exys.org>
	<20100114183854.1d04f111@hikari> <87fx68e2am.fsf@yoom.home.cworth.org>
	<slrnhkvo6d.2rf.olly@msgid.survex.com>
	<878wbzx3td.wl%djcb@djcbsoftware.nl>
	<slrnhl06bt.2rf.olly@msgid.survex.com>
	<87pr5bw383.wl%djcb@djcbsoftware.nl>
Date: Fri, 15 Jan 2010 12:15:24 -0800
Message-ID: <876373dt0j.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Cc: notmuch@notmuchmail.org
Subject: Re: [notmuch] indexing mail?
Precedence: list

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Fri, 15 Jan 2010 21:57:32 +0200, Dirk-Jan C. Binnema <djcb.bulk@gmail.co=
m> wrote:
>     Olly> Underscore prefixed identifiers are reserved by ISO C at file-s=
cope;
>     Olly> using them yourself is undefined behaviour...
>=20
> Ah, thanks for reminding, I thought it was __ and _C (capital), but you a=
re
> right:
>=20
> ,---- (7.1.3 Reserved identifiers)
> |  All identifiers that begin with an underscore and either an uppercase =
letter
> |  or another underscore are always reserved for any use.
> |=20
> | =E2=80=94 All identifiers that begin with an underscore are always rese=
rved for use as
> | identifiers with file scope in both the ordinary and tag name spaces.
> `----

But please don't be too strict about this.

Please feel very free to use any identifier with a _notmuch prefix.

And really, feel free to use just about any underscore-prefixed
identifier that you want that doesn't clash with anything on your
system.

Then if we do identify an actual clash somewhere then we can fix it.

I think it was stupid of Posix to steal _ and a reserved prefix, and I
really don't have a problem ignoring that. This is like I described in a
recent mail---trying to prevent all portability problems just isn't
worth the effort. It's much easier to fix problems that actually occur
in practice.

=2DCarl

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLUMzd6JDdNq8qSWgRAmh/AJ9oRSoe9/H32Wu8JqEMv0HBm55OnwCfT0N7
z5WdgEgWvZkXMW2VL/phfX4=
=Rr1C
-----END PGP SIGNATURE-----
--=-=-=--