[Pyrex] Pyrex at Pycon

[Greg Ewing]

Matthias Baas <baas at ira.uka.de>:

> Of course, it would be nice if Pyrex could output a report that contains 
> all #defines so that I can go through them and decide how to add them to 
> the *.pyx file.

That's probably doable -- I think gcc has an option to
get a list of all preprocessor definitions made.

> The preprocessor output still contains lines that name the input file 
> from which the following lines are taken. So it'll still be possible to 
> ignore lines that are not from the currently processed file or that are 
> stored in an entirely different directory tree, etc.

That's a good point. I'll keep these ideas in mind.

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
greg at cosc.canterbury.ac.nz	   +--------------------------------------+