Cart
|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Must databinding imply tight coupling? (was Re: Newtool f
Dare Obasanjo wrote:
> Hardened XML geeks would prefer using an XML API that doesn't
[expletive deleted]. 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 [expletive deleted].
Bill de hÓra
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||
