Re: WO vs. .Net 3.5 LINQ
Helge Hess <[email protected]> Sun, 2 Dec 2007 00:20:32 +0100
| Newsgroups | gmane.comp.web.webobjects.general |
|---|---|
| Message-ID | <[email protected]> |
On 01.12.2007, at 23:25, Miguel Arroz wrote: > On 2007/12/01, at 22:12, Mike Schrag wrote: >>> In MS's defense, LINQ is more abstract than that, and a LITTLE bit >>> interesting ... For instance, you can construct a LINQ query >>> against an XML document (so it effectively behaves like XPath, but >>> in a unified query language). > Humm.... that seems... Core Data? :) Hm, no, isn't the XML of CoreData just a CD specific dump of the in- memory objects? To me it sounds more like KVC on a DOM node. (evaluateWithObject() called on a DOM node which obviously needs to provide a sensible KVC=>XML mapping). (valueForKey on a DOM node could do all kind of funky things) Language wise I'm not sure whether LINQ is a particulary good idea, IMHO the only real application is SQL generation (well, or other stuff which will be executed in a different process, IMAP4 or LDAP queries would also be OK). For stuff which is processed by the appserver HOM/blocks look like a much more beautiful solution. Greets, Helge