[Python-3000] how about switching to a preprocessor? (Re: A better way to initialize PyTypeObject)
Barry Warsaw
barry at python.org
Sat Dec 2 22:08:27 CET 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Dec 2, 2006, at 3:58 PM, Neil Toronto wrote:
> One potential problem with this idea is that you can't drop into C
> code
> without calling an external C function, which may not be acceptable in
> some instances. Another is that if you want to analyze the performance
> of your code, you at least have to *look* at the C code it generates,
> which is a bit icky. I think that's pretty much going to happen no
> matter what though, unless the preprocessor is only a very thin
> wrapper
> around C.
We need to keep in mind things like debugging and code discovery
(IDE, tags, grep), when talking about requiring the use of a
preprocessor for extensions. For an application like ours that is
very heavily embedded/extended I'm concerned how difficult it will be
debug, develop, and maintain these generated extensions. Generated
code can be a big time saver while you'r developing the code, but
eventually you have to go digging into it, then it's always way more
painful.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRXHrUHEjvBPtnXfVAQJdGwP/dCFh8+8PeGOdVWeDlhktIEA+ljUKePRW
Bu6vbiWNkxiBBRDWyYcNJBWGhwRC/BE7aQuxGZa3s/LyMpjFpU7xY+8DxEwsORUD
C9zKYp9hNN3RB+YnB4zrTMb5sNL/Xeblj33pLUpF22YV49mAayKnhI5pK7e/Z+3T
VznlRMElACc=
=f928
-----END PGP SIGNATURE-----
More information about the Python-3000
mailing list