Jan. 13, 2003
9:55 a.m.
On Sun, Jan 12, 2003 at 02:32:54PM +1300, Andrew McGregor wrote:
Therefore a Pythonic macro should be:
A class which adds it's grammar
... Then the macro provides code which is called with the parse trees resulting from that grammar, modifies them, and returns the parse tree that will actually be compiled. If you want to evaluate some bits at compile time, do that explicitly in the macro (opposite way around to lisp, where you have complicated rules).
I want that! Here is an interpreted language that does that : http://pliant.cx/ Fully GPL. Source available. Worth a look. -- Nicolas Chauvat http://www.logilab.com - "Mais où est donc Ornicar ?" - LOGILAB, Paris (France)