Dag Sverre Seljebotn wrote: > I guess I should repeat my big -1 for this then. > > I think Java-like behaviour is much more appropriate (i.e. raise proper > exceptions in the code using the variable, but allow None as a value).
This may indeed be a better way for Cython to go, given its goal of matching Python semantics. I don't think it's right for Pyrex at the moment, though, because making it efficient would require rather more analysis than I'm intending to do in the foreseeable future. > Let's not break the language forever I don't think it needs to be broken forever. If I ever decided to do None-checks at time of use, I could just stop taking any notice of 'or None' and 'not None' declarations. They would be allowed so that old code would still compile, but they would be ignored. -- Greg _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
