On Fri, 15 Aug 2008, Greg Ewing wrote: > Dag Sverre Seljebotn wrote: > >> So I propose this change: There is a cutoff in the pipeline at which >> stage errors are reported (and if any, processing stops). > > That sounds reasonable. You could even go further and have > a cutoff after every stage of the pipeline, so that any > stage can assume it has valid data from the previous stage.
Often it is useful to maximimize the number of errors caught in a single invocation of the compiler. One thing I hate doing is (run the compiler, fix the only reported error) x 10. > A refinement would be to have "fatal" and "non-fatal" > errors, where fatal errors terminate compilation at > the end of the current pipeline stage. This sounds like a very good idea. Non-fatal errors would result in a valid tree that could be carried on to the next stage, but invalid compilation. It might be to hackish, but we could also run each stage in a try-catch, and if it catches any Exceptions after a "non-fatal" error it silently ignores them. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
