On Wed, 01 Jul 2009 09:42:31 +0400, Dmitriy Sintsov wrote:
XSLT itself is a way too much locked down - even
simple things like
substrings manipulation and loops aren't so easy to perform. Well, maybe
I am too stupid for XSLT but from my experience bringing tag syntax in
programming language make the code poorly readable and bloated. I've
used XSLT for just one of my projects.
I'd assume we want locked down. Loops would be hard in any locked-down
environment; I don't recall seeing any recommendation in this thread on
how that wold be done. Recursion is much simpler, just track the depth,
and throw an exception if it goes to deep; emacs lisp already uses this
mechanism.
Some of those things may not be as easy as other lanugages, but the string
functions that this thread was started over are built into XPath 2.0, so
it would solve the problem at hand.
Deeply nested braces of lisp remind me of current
MediaWiki parser.
Superficially, sure; but IMHO the real problem with the current parser is
the ambiguity, that when you see a construct begin like {{{{{something...
you need to keep reading before you can parse it. With lisp, it's trivial
to parse, so we could do our own parsing if needed.
Lua was highly valued here at computer lab, also Ocaml
(not sure of
proper spelling).
Dmitriy
It seems like there are benefits there, but it's less clear how to
implement that sufficiently locked down, and how that would interface with
the rest of the parser, for callbacks, magic words, etc.