> Meanwhile, I'm wondering if it is worth trying to add some syntactic sugar to > make anonymous macros easier to use. My initial thoughts (but only lightly > tested) is that something like this would make it easier to write macro > definitions which in turn define other (possibly anonymous) macros:
This m4_(un)defer seems okay and it makes sense to do it automatically within m4_lambda. But the need to use dquote escapes me, and it seems to make m4_lambda close to unusable in practice, except for forwarding to another macro in ways more advanced than what m4_curry allows. Can you explain? Paolo