This is a summary of the responses I've got on #perl6 irc.
I'm sending the follow up to perl6-compiler only; I guess this is off-topic in perl6-language. 2007/6/19, Flavio S. Glock <[EMAIL PROTECTED]>:
I'm looking for comments on how to improve the compiler internals. For example: - One of my basic design principles was to implement AST transformations as "pluggable" modules, using a visitor pattern. Do you see potential problems with this approach?
No problems with the visitor pattern, but the way that "aspects" are implemented in the AST-plugins might cause hard-to-detect errors. For example, if the AST is changed in one place and the AST-plugin is not updated, no error will be reported (pmurias++).
- BEGIN block side-effects are recorded in a hash. This adds an overhead to all assignment operations. Do you see a better way to check for side-effects?
This will probably be discussed in an irc meeting scheduled for next week. Yesterday, we discussed the way the compiling environment is represented internally. It's complex, but it works. We don't have a simpler solution yet.
I'd appreciate if I can get a compiler architecture review. I'm available on #perl6 in freenode (my timezone is -03:00). You can find me there as 'fglock'. Please share your comments either here on the mailinglist or via IRC. I look forward to your feedback
thanks! - Flavio S. Glock (fglock)
