Carl Witty wrote: > On Tue, Aug 5, 2008 at 8:34 AM, Stefan Behnel <[EMAIL PROTECTED]> wrote: >> Dag Sverre Seljebotn wrote: >>> There is >>> not really such symbol as cython.boundscheck in the scope, it is a magic >>> option only. So of course you cannot do >>> >>> a = cython.boundscheck >>> @a >>> ... >> Fine with me. > > Hopefully this will fail at compile-time rather than runtime?
Thanks!, good point. No, I need to fix this (it disappears from scope and thus is deferred to runtime for lookup..) >>> d) A with statement: >>> >>> cimport cython >>> with cython.boundscheck(False): >>> ... >>> >>> The entire with statement is then stripped out of the source prior to >>> the with transformation. >> Fine. We should take a little care that we document directives that cannot >> be used that way, e.g. because they only apply to functions and not to >> simple blocks (not sure we ever need that, just a side-note). > > Again, such directives should fail at compile-time. (The restriction > should be documented, too, of course.) Yep, this one is a no-brainer and easy to do (once we have such an option to do it with). -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
