On 2/15/06, Nick Coghlan <[EMAIL PROTECTED]> wrote: > Thomas Wouters wrote: > > On Wed, Feb 15, 2006 at 07:28:36PM +1000, Nick Coghlan wrote: > > > >> On the 'unusable AST' front, if AST transformation code creates illegal > >> output, then the main thing is to raise an exception complaining about > >> what's wrong with it. I believe that may need a change to the compiler > >> whether the modified AST was serialised or not. > > > > I would personally prefer the AST validation to be a separate part of the > > compiler. It means the one or the other can be out of sync, but it also > > means it can be accessed directly (validating AST before sending it to the > > compiler) and the compiler (or CFG generator, or something between AST and > > CFG) can decide not to validate internally generated AST for non-debug > > builds, for instance. > > > > I like both those reasons. > > Aye, I was thinking much the same thing. >
Yeah, I would want it to be a separate part as well. -Brett _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
