Now that compiler directives will become really important for some folks we should solve this.
First, it seems that "--directive" can be used to set compiler directives from the command line; however there's no shortcut (despite the command line documentation, the -X switch is used for some Mac OS X experimental stuff -- can we remove this and use -X for the directives? --link could still be used for the Mac OS X thing). Secondly, I propose a change of priorities. Currently a directive is set by these precedence rules (i.e. start at the top of the list and continue until a setting is found): 1) with statement and decorators w/ block level 2) command line switch --directive 3) #cython comment at top of file 4) builtin defaults Now that we see what kind of things this can be used for (i.e. cdivision), I propose that the 2) and 3) are exchanged, so that #cython comments take precedence before command line. If there's a need for the current behaviour, we could introduce #cython default: nonecheck=True or similar as another mechanism to be checked after the command line. -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
