Dag Sverre Seljebotn wrote: >>> (Well, at least two people (myself and Robert) has opposed this being >>> the default (and not for reasons of backwards compatability!), so I >>> don't think we're at the stage where we can discuss deprecation just yet >>> :-))
My point was that IF any backward incompatible changes were made, there should be a reasonable deprecation procedure. Whether the change should be made or not I'll leave to others -- what seems obvious to me could well be a function of my very limited use of Cython so far. What I do know is that the current behavior is a surprise to newbies -- a bit more documentation may be all we need. >> If a faster "nonecheck" was added >> then "not None" would be a really redundant part of the language. Is that possible (well, not "faster", but fast enough not to notice). My understanding of nonecheck is that a check has to be done on every object access (Or index, or...). In a tight loop that indexes through a numpy array and does very little, that just doesn't seem practical. Or could you put the check outside the loop, but not at the beginning of the function? >> So I wouldn't phrase the FAQ entry just like that myself, feel free to edit, of course. >> Myself I tend to advocate adding an if-test in the function instead.) Why is that? I like "not none" it's clear, and it seems belongs in a type declaration. But anything that works... > Whoops. I got the smiley the wrong way, it should be ":-)" no problem -- I read it as a smiley anyway. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected] _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
