Hi there,
A smaller patch could be constructed following the same principle I
used in my previous mail to handle just logging. If we made the log
function be passed through options (if no log function is supplied,
the empty function is passed in), we could make logging entirely
configurable. This is more flexible than a lot of particular hooks to
do logging as I write in the previous mail.
I realize that this is shooting down some of my arguments in my
previous mail. That's fine; I just want good code.
What should be the principle to determine whether we want *specific* hooks?
I'd say we only want explicit hooks at those points in the code where
language construct directives are being handled, such as {.section},
{.end} and {.repeated section}. It should allow you to construct a set
of hooks that inserted comments equivalent to the directives in the
output, for instance <!-- {.section foo} -->.
Regards,
Martijn
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "JSON
Template" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/json-template?hl=en
-~----------~----~----~----~------~----~------~--~---
