Hi, Helvetia requires a couple of things: - Flexible parsing. Lukas built PetitParser for this and now PetitParser2 is even faster and more powerful (for example, with bounded seas parsing) while preserving the same flexibility. - Flexible compilation toolchain. At the time, Lukas employed a significant amount of overrides. Now we have Opal which makes this step easier. - Moldable development tools. GT was designed with moldability in mind so at least the debugging part should be easier to handle. We still need work in the area of syntax highlighting, completion and editing.
Cheers, Doru > On Mar 2, 2017, at 9:12 PM, H. Hirzel <[email protected]> wrote: > > Hello Doru > > On 3/2/17, Tudor Girba <[email protected]> wrote: > ..... >> That said, I do want to have mechanisms that allow us to embed other >> languages and DSLs in our environment. In this area I prefer the approach >> put forward by Helvetia because it is not invasive and highly flexible (and >> now should even not be expensive to have anymore). > > Just wondering what you mean by this. > Could you please elaborate a bit what you mean that it would now be > less expensive to have a Helvetia system in Pharo? The last time it > was implemented was in Pharo 1.1.2 ** > > Regards > Hannes > > **http://scg.unibe.ch/research/helvetia -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."
