Re: [xml-dev] Must databinding imply tight coupling? (was Re: Newtool for handling XML in Java)

[Bill de hÓra <bill@dehora.net>]

Dare Obasanjo wrote:
 > Hardened XML geeks would prefer using an XML API that doesn't 
suck. His code takes two lines of readable code using .NET Framework 
APIs without having to resort to a data binding technology. A 
compilable example follows
 >
 > using System;
 > using System.Xml;
 >
 > public class Test
 > {
 >
 >    public static void Main(string[] args) {
 >      XmlDocument doc = new XmlDocument();
 >      doc.LoadXml(@"<stock>
 >                      <price>4</price>
 >                      <expenses>4000000</expenses>
 >                      <revenues>8900000</revenues>
 >                    </stock>");
 >
 >      //!!!!ONE LINE OF CODE !!!!
 >      double PEratio = (double)
 >        doc.CreateNavigator().Evaluate("/*/price div (/*/revenues 
- /*/expenses)");
 >
 >      Console.WriteLine("PE Ratio = {0}", PEratio);
 >
 >   }
 > }


In your not-really-one line example I particulary like the 
combination of typing styles and various unsafe coercions. All of 
which tell me the language is just... in the way. Something like 
this would be preferable:

target = "<stock><price>4</price>\
<expenses>4000000</expenses>\
<revenues>8900000</revenues></stock>"
func = "/*/price div(/*/revenues - /*/expenses)"
peration = evaluate(func, target)

Hardened XML geeks would prefer using a programming language that 
doesn't suck.

Bill de hÓra