Well, if we add "static" we start getting unused GCC warns .. So I've decided to change this to a #define'd macro... Just in case, I've not removed the definition in Naming.py.
On Fri, Apr 17, 2009 at 2:56 PM, Robert Bradshaw <[email protected]> wrote: > On Apr 17, 2009, at 7:49 AM, Stefan Behnel wrote: > >> Lisandro Dalcin wrote: >>> Sorry, I did not understad you comment, perhaps I was not clear >>> enough... This is a global var, not one loca to function, then I'm >>> asking to emit the C code like this: >>> >>> static const char *__pyx_modulename = "mpi4py.MPI"; >> >> Yes, that's what I meant. It's not supposed to be used anywhere >> outside of >> the module, so "static" is correct here. I assume that Robert added >> the >> constant because utility functions are not currently module specific. > > Yep, IIRC, I needed to provide the module name in the warning. The > above should be totally fine. > > - Robert > > > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev > -- Lisandro Dalcín --------------- Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC) Instituto de Desarrollo Tecnológico para la Industria Química (INTEC) Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET) PTLC - Güemes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594 _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
