[Numpy-discussion] Exported symbols and code reorganization.
Charles R Harris
charlesr.harris at gmail.com
Sun Jan 7 13:07:15 EST 2007
On 1/7/07, Robert Kern <robert.kern at gmail.com> wrote:
> Charles R Harris wrote:
No, but as with mtrand, most of those arise from the fact that these
> are implemented in files other than the C file that contains the Python
> code. In order for them to be called from the Python module code, they
> need to
> be exported, IIRMCC (If I Remember My C Correctly). This appears to be
> true of
> essentially every other extension module in my site-packages, so I don't
> it's going to be much of a problem.
I don't think unnecessary public symbols are much of a problem, either, but
it bears on the question of breaking up the core numpy files. The parts
could be treated in the same way, i.e., compiled separately and linked, or
they could be treated as you suggested previously, declared static and the
code included into one base file. I suspect the inclusion route is a bit
easier from a portability standpoint, long link lists can be a problem and
the making of libraries is platform dependent.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion