Robert Bradshaw wrote: > On Jan 15, 2009, at 5:04 PM, Michael Abshoff wrote:
<SNIP> Hi Robert, >>> Thanks for looking into this--from what I understand of what you sent >>> it's symbols like "min" and "set" that are getting exported to the >>> namespace that weren't before? >> >> Yes, I avoided the term namespace since there is no meaning like >> that in >> C as I assume you all know well. > > Yeah. Scope would be a better word, and there's only one global one. :) - having a discussion about Cython, C and C++ at the same time makes using technical terms more than a little ambiguous. >>> I'm not sure what happened between >>> 0.10.3 and now that would call this--did anyone include any new >>> headers? >> I don't know, but I assume you mean this in the context of Cython. > > Yes, I'm meaning in the context of Cython. Either that or someone > changed how (C++?) files get processed. I certainly haven't done > anything in that area, but it's possible that someone else did. This isn't just C++, i.e. the pari failures, the quaddouble and others are all pure C issues unless NTL is pulled for example in those cases. > A random thought, this couldn't be an artifact of all the char* -> > const char* changes, could it be? Given that this is also a C issue I cannot see how this could cause the problem, but given my experience over the last year on porting Sage I can tell you that the impossible seems to happen weekly and I have to eat my hat because of that quite often :) > - Robert Cheers, Michael > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev > _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
