From: Sebastian K. <seb...@mu...> - 2003-06-21 13:00:38
|
Hi Keats, On Saturday 21 June 2003 00:06, Keats wrote: > I've finally gotten back to work on the #templet an #eval directives. I > thought I'd give an update and solicit some feedback. I'm wondering, whether #eval should really be a directive. I think I dislike it, because you don't have a choice anymore, what to do with the evaluated templet: It always gets printed. Remember Lane's wish to store templet's somewhere out of a wm-file? My proposal was to create a "Writer"-Tool, that can take any macro and store it somewhere. So with your proposal, you could do #template $t { bla bla blub blub $foo $bar } $Writer.write("some/file.txt",$t) if $t is a macro, but if you want to change the context, you couldn't. But if you would add a method "withContext(Map context)" to $t, you could do $Writer.write("some/file.txt",$t.withContext({"foo":"a", "bar" : "b"}) Do you understand my point? What was the reason for needing an #eval-directive in the first place? Sebastian -- Sebastian Kanthak PGP/GnuPG: http://www.muehlheim.de/~skanthak/pgp.html |