RE: [Falcon][Discuss] Modularity, extensibility and configurability of the Falcon compiler framework

2013-01-28 Thread Michael A. Labriola
>In the spirit of understanding, with a prototype we are going to develop it in >a non intrusive way to the existing compilers. There is no plan to go hacking >into the existing code if we don't >have to at this point, plus that would be >completely stupid IMHO. > >I think the proof of concept w

Re: [Falcon][Discuss] Modularity, extensibility and configurability of the Falcon compiler framework

2013-01-27 Thread Erik de Bruin
Roland, Me likey. Some comments and suggestions inline: > I think it might make more sense to create a single point of entry for all > types of compilation. Let's call this point of entry FLEXC (credit: > Michael Schmalle). Wouldn't it be cleaner to use this FLEXC compiler as a > sort of factor

Re: [Falcon][Discuss] Modularity, extensibility and configurability of the Falcon compiler framework

2013-01-27 Thread Michael Schmalle
+1 on this. FYI, As the Apache way suggests, itch your scratch... This one is going to happen and I will be working on it with Roland. We are looking for constructive criticism, not a blessing. :) I already have 2 compilers to work with and it's ridiculous one parse session can't be used

[Falcon][Discuss] Modularity, extensibility and configurability of the Falcon compiler framework

2013-01-27 Thread Roland Zwaga
Good day to all of you :) Hold on, I think this is going to be a long message... Moving on from the latest discussion between Erik and Frank about the ideal implementation of AS->JS cross-compilation, I think its perhaps an interesting venture to talk a little bit about some possible changes we c