From: parrt@...
Date: 2008-10-02T10:13:52+09:00
Subject: Re: my ears are burning... ;)

> I got stuck with ANTLR's Ruby templates due to a lack of documentation
> of what data was available to each template. I guess it's just a parse
> tree representation of some sort, but I wasn't familiar enough with
> ANTLR to figure it out. An ability to define a template as "Stub - print
> a diagnostic telling me all the things available here" would have helped
> a lot.

Well, easiest way to look at that is to examine the argument list of
the template itself. That tells you the name of all attributes
visible; well, it does not include the attributes visible from the
enclosing template. That is the hard part with dynamically typed
languages like Ruby, Python, and ST. You know the name, but can't
remember the type. ;) In this case, you never knew the type. ha! You'd
need to look at how the closest language implemented the target. Then,
monkey see, monkey do. One of these days, I will write up the
architecture. I note with some satisfaction that the guy building the
Lisp backend is having no trouble.

Ter