[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] LINQ to XML versus XSLT
Subject: Re: [xsl] LINQ to XML versus XSLT From: Colin Paul Adams <colin@xxxxxxxxxxxxxxxxxx> Date: Fri, 27 Jun 2008 16:10:22 +0100 |
>>>>> "Alexander" == Alexander Johannesen <alexander.johannesen@xxxxxxxxx> writes: Alexander> On Fri, Jun 27, 2008 at 16:33, Colin Paul Adams Alexander> <colin@xxxxxxxxxxxxxxxxxx> wrote: >> But I don't agree that it is a good idea. What should the type >> look like? Certainly not the W3C DOM. Alexander> DOM was yet another inbaked API, nothing more. No, XML Alexander> as native to languages should, IMHO, look like XML, Alexander> where <result> = <value>{$variable}</value> + Alexander> <value>{$other}</value> ; becomes ; Alexander> <result> <value>...</value> <value>...</value> Alexander> </result> That's just STRING. At least, so it appears to me. Alexander> I'm sure if a bunch of people think about this for a Alexander> little while we could come up with something that's Alexander> pretty cool, and urge languages to adopt it. I'm sure they couldn't. What should the processing characteristics be? Should it be optimised for streaming processing, or for the XPath preceding-sibling axis or ... ? -- Colin Adams Preston Lancashire
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] LINQ to XML versus XSLT, Alexander Johannesen | Thread | RE: [xsl] LINQ to XML versus XSLT, Scott Trenda |
Re: [xsl] Making Two Variables In T, Andrew Welch | Date | RE: [xsl] LINQ to XML versus XSLT, Scott Trenda |
Month |