[stringtemplate-interest] IronStringTemplate

[Terence Parr]

On Jun 29, 2009, at 2:09 PM, Robert Byrne wrote:

> I think I've figured out a way to do all I need with the current
> implementation, by overriding the template lookup process, which was  
> the
> only real question mark.
>
> Now the only reason to roll my own implementation would be for the
> educational value of building the translator via ANTLR + DLR, I may  
> tinker
> with it in my free time if I can't find a better solution looking  
> for a
> problem :)
>
> Looking fwd to the next version, is there a roadmap?

I took a bunch of  notes at the workshop in early June. My summary is  
that current language and dynamic nature is spot on. What I need are  
better debugging tools and more consistency with errors and better  
error messages and so on. There are a number of new little features to  
add.	I'm not going to directly support a generation model. I'm going  
to re-implement the interpreter as either a command interpreter or a  
register-based interpreter.

Ter