Re: xsl:lambda was RE: W3C-transformation language petition

Hi Jonathan.

This isn't the first time I've seen discussion of LISP as a good example of
a declarative language, with relevance to XSL.

Can anybody recommend some good primer material on the Net? I'm not
interested in learning LISP for application development, just to see what I
might learn about declarative models in general, and specifically how it
relates to XSL. Something discussing LISP methodologies as they might
differ from traditional imperative methodologies would be ideal.

Thanks for any pointers.

Cheers
     Guy.





xsl-list@xxxxxxxxxxxxxxxx on 03/09/99 08:19:02 AM

To:   xsl-list@xxxxxxxxxxxxxxxx
cc:    (bcc: Guy Murphy/UK/MAID)
Subject:  xsl:lambda was RE: W3C-transformation language petition




[SNIP]
        my first inclination was to suggest that a free Java DSSSL/Scheme
implementation might do for client side transformations what XSL does (or
might do) and more...
...but when you think about it, this might not be true... HTML is alot
closer to XML than Lisp in its syntax and HTML remains the most important
output format if we are concerned about client side applications.
what I am interested in doing is employing XSL as a client application
'language' for browser based client apps. So, what I need for XSL is to
grow
into something akin to an XML based Scheme.  It already has a cons and car
and cdr and eq. XSL needs a lambda and defun and recursion. That's the
stuff
that ought be between <xsl:eval> rather than Javascript.
Jonathan Borden
http://jabr.ne.mediaone.net

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list






 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list