Given build-markup is only in the betas (as far as I'm aware), I thought I'd
make a couple of criticisms it gets concreted into the released language
with that name.
This is no critisism of the actual code of build-markup because it does add
value.
However, I believe build-markup to be misnamed. It really only takes a
string! and emits a string!, and if you review it, it does not in any sense
process markup at all. It really is only a sophisticated string based
replace/all. For example:
>> build-markup {The time is now <%now/time%>}
== "The time is now 17:17:36"
Load/markup returns tags and strings - it at least ackowledges that markup
consists of tags and strings. The output of Build-markup cannot be passed to
load/markup in all cases.
In summary, nowhere in build-markup is there any meaningful reference to
markup. A build-markup function should take a dialect [block!] as input in
order to produce a string.
I'd like to see it change name.
Am I off track here?
Comments?
Brett
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
