-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jan 3, 2007, at 2:29 PM, Martin v. Löwis wrote:

> Guido van Rossum schrieb:
>> Maybe this should be done in a more systematic fashion? E.g. by  
>> giving
>> all "internal" header files a "py_" prefix?
>
> Yet another alternative would be to move all such header files into a
> py/ directory, so you would refer to them as
>
> #include "py/object.h"
>
> Any preferences?

I think I prefer this, although I'd choose "python/object.h" just for  
explicitness.  But if you go with a header prefix, then the shorter  
"py_" is fine.

FWIW, I tried to do a quick grep around some of our code and I found  
that the only "internal" header we include is structmember.h.  Why is  
that not part of Python.h again?

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iQCVAwUBRZwJ+nEjvBPtnXfVAQL55wP/SxjN9/ncb86KnhRMUf24U6fp+u5JrpN3
irJfi/3tf9iXFtHXPkvkc4hEM9DkF8pa+jYDICG1pZ2J0YQD/AcSuB52WoWDwBtn
BIKt1QmJvxgWZLW+dAekWhgSD95laPw+72iCwBvFlIP3+IXtF/Fw9AtuxiGwQzE3
R71j5tZAde4=
=nA9B
-----END PGP SIGNATURE-----
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to