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 will

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

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 factory