RE: lua & E4X ?

["Greg McCreath" <Greg.McCreath@...>]

Hi All,

Thanks for the replies.

Looks good, but not quite what I was meaning.  Consider how lua would do something like (say) AJAX.

Yes, XML handling is often awkward, but E4X has a very natural feel to it.  This is about being able to call an XML API from within lua and then deal with the results in a meaningful way that is more than a raw tree of tables.

I do like the element.sub-element.sub-element.@attribue-name type syntax of E4X and it's not too far away from lua syntax is it.  Javascript also uses associative arrays a lot.

Perhaps one approach is token filtering to turn the '@' into a call to a special sub-table (or something) representing the attributes.  This doesn't address the query like nature of E4X syntax to get at a list of elements, perhaps in this case, another special token could be used.  Not sure, I'm not that familiar with the new token filtering capabilities.

However, there is nothing about this that would stop you shoving any old table in at any point of the tree and destroying the integrity of the XML tree structure.

At in case, I do agree, trying to address the issue of expressive and safe XML manipulation using a tree of tables is quite second-rate.  Hence the posting to the group.

All comments and input appreciated.

Greg.


-----Original Message-----
From: Javier Guerra [mailto:javier@guerrag.com] 
Sent: Thursday, 8 March 2007 8:14 AM
To: Lua list
Subject: Re: lua & E4X ?

On Wednesday 07 March 2007, Wilfred wrote:
>  Hi Greg,
>
>  I would be interested in discussing a common API for Lua.

i've done several tests, trying to find a 'comfortable' way of handling XML in 
Lua.

parsing is (almost) OK with SAX-type APIs, but directly modifying XML is 
challenging.

i realized that a big part of the problem is the syntax.  since XML is a 
horrendous mismatch of features, it's very hard to map it to a simple 
structure.  one naïve attempt would be to map all to a tree, but then text 
content and attributes would be 'special' nodes, and in the end you get a 
monstruosity like DOM.

after a quick glance, E4X looks like DOM without the functions.  that is, XML 
is handled as a tree of objects, with all the quirks of non-tags tree nodes.

so, if it's so hard to come up with a syntax that can express every XML 
(mis)feature, why not use XML itself?

so far, my preferred solution is to turn it backwards: using XML as a template 
that calls Lua for output.  at this time, the lua callbacks have access to 
several other pieces of already-parsed XML, and make it easy to modify 
locally or globally.

the template doesn't have any Lua code, and the Lua code doesn't have any XML 
content.  the only common things are: functions names in the template, and 
you can use attributes, tagnames and tag IDs in Lua.

for example, a template might include this:
----------------- xml --------------
	<tbody function="sched_body">
		<tr>
			<td function="row_var" varname="task" />
			<td function="row_var" varname="priority" />
		</tr>
	</tbody>
---------------- xml end ------------
and the Lua code:
----------------- lua ----------------
require "xlp"

local page = xlp.new_page (in_f, out_f)

function page.cb.sched_body (node)
	page:out_tagstart (node, false)
	for i = 1,10 do
		page:out_content (node, i)
	end
	page:out_tagend (node)
end

function page.cb.row_var (node, row)
	local varname = node.attr.varname
	return xlp.new_node (node, string.format ("%s(%s)", varname, row))
end

page:out()
-------------------- lua end --------------------

the call to xlp.new_page () parses and optimizes the XML.  after that, you can 
populate the callback table (in page.cb) with functions.  the call to 
page:out() processes the XML, calling your Lua functions.

the output looks like:

	<tbody function="sched_body">
		<tr>
			<td function="row_var" varname="feature">feature(1)</td>
			<td function="row_var" varname="task">task(1)</td>
		</tr>
		<tr>
			<td function="row_var" varname="feature">feature(2)</td>
			<td function="row_var" varname="task">task(2)</td>
		</tr>
		<tr>
			<td function="row_var" varname="feature">feature(3)</td>
			<td function="row_var" varname="task">task(3)</td>
		</tr>
	</tbody>

there are a few more features, like being able to reference any XML subtree 
that had an ID, and a very simple function to turn a XML template into a 
Xavante page handler.

if anybody is interested, i might try to document it

-- 
Javier



This email and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. This email may contain personal information of individuals, and be subject to Commonwealth and/or State privacy laws in Australia. This email is also subject to copyright. If you are not the intended recipient, you must not read, print, store, copy, forward or use this email for any reason, in accordance with privacy and copyright laws. If you have received this email in error, please notify the sender by return email, and delete this email from your inbox.