On Mon, Dec 6, 2010 at 10:50 AM, Robert Bradshaw <rober...@math.washington.edu> wrote: > On Sun, Dec 5, 2010 at 9:47 PM, Stefan Behnel <stefan...@behnel.de> wrote: >> Ondrej Certik, 06.12.2010 02:42: >>> Maybe we should create a StopOnFirstError >>> exception, and then catch it and print "exiting the compilation due to >>> --fatal-errors command line switch"? >> >> +1, although I'd name it AbortCompilation or something like that, maybe >> SilentlyAbortCompilation. > > We should trigger the exact same kind of abort that happens between > (some) pipeline phases if there are any errors. This will trigger the > necessary cleanup (e.g. a castrated C file), etc. I thought that's > what I did, but I guess I only tested running cython manually (which > didn't give a nasty traceback). > > While I'm thinking about this, I'd rather the flag be named > --fast-fail, as errors are always fatal, it's just a question of > timing.
Sure. Can you make this change before the release? So that people don't start using the other option. I just followed the gcc naming convention, to stay compatible. Gcc uses -Wfatal-errors. Ondrej _______________________________________________ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
