Tool development: by Perl-wrapped XQuery

[David A. Lee]

>
>> * Use a scripting language that already is 'in process' with all the
>> XML core languages you want to use (xquery, xslt etc)
>>  -> examples XProc, xmlsh
>>
>> * Encourage scripting languages developers to embed these XML
>> languages directly into the scripting languages (say perl).
>
> More precisely, write bindings to implementations in C/C++.
>
Only if the scripting language itself is written in C/C++ or has easy 
bindings to it.  If its in another language then bindings in that 
language are useful.

But equally important, IMHO,  is to be able to "glue" the data from one 
module to another efficiently.  That needs common in-memory formats.
And a way in the language to make calling these modules and passing data 
to/from them easy in a way thats 'natural' for that language.
That may mean, for example, that the language runtime define a standard 
XML in-memory representation and every module can use it natively.
So that you can have say variables of XML Documents and not have to 
transform them to each module's internal representation (rebuild the 
document).

To do this well I suggest is more then just writing bindings.  Its a 
language level problem as well as a binding problem.

-D






David A. Lee
http://x-query.com/mailman/listinfo/talk  
http://www.calldei.com
http://www.xmlsh.org
812-482-5224