OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] Declarative XML Processing with XQuery

[ Lists Home | Date Index | Thread Index ]

Hjelsberg's discussion takes a bit longer to absorb but 
is well worth it.

Thanks.   Off the top, some of what I like about Foxpro 
comes back with the language integrated query.  There 
is a lot more, but I leave that to the language 
junkies (of course, passing code as data is productive).

When I consider how much time and energy was devoted to 
getting data separated from the code, it is a little 
scary to see that much code dedicated to putting it back. 
Still, I don't see new applications here.  The reason 
for the comparison to the days of markup prior to XML 
when the users dominated the ecology.  The closer one 
gets to language design, the less one is thinking of 
applying a language.  A danger of integrating XML and 
programming languages is forgetting that the application 
user, the domain expert, may not wish to program given 
it is an "inherently career limiting" skill.

So why exactly do we want to use XQuery or XLinq?  
 
One reason, with my limited practical experience, that 
comes to mind is that this is a lot like Foxpro in that 
Foxpro, being a dedicated database programming language, 
was a lot more productive than doing the same work in say, 
Visual Basic.  Having the queries in the procedural language 
(once one mastered USE) was quite powerful and real rapid 
prototyping.  

len


From: Michael Champion [mailto:michael.champion@hotmail.com]

... Anders  of the evolution of 
mainstream languages to be more declarative in 
http://microsoft.sitestream.com/PDC05/TLN/TLN307_files/Default.htm#nopreload
=1&autostart=1




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS