XQuery and Item Orientation

[Brian Maso]

1) C Omega's name is bizarro -- technically it is "C-<lower-case-omega>",
which looks more or less like "Cw" when you try to make something like it in
latin letters. "Cw" is of course unpronounceable, so many people refer to it
as "Cu". (C Omega tops C# for poorly-conveived name. Google didn't index on
the "#" character when C# was originally released, so searching for "C#" in
Google originally yielded nothing. "C-<lower-case-omega>" yields even less.)

2) I really have no knowledge of relative performance/expressiveness of the
language approaches you are asking about. I must admit I am intigued by the
idea of polymorphism based on XPath pattern -- its kind of like ML/Scala
pattern matching on steriods I guess -- I'm hoping you will go forward with
it a bit and we can see where it leads!

Brian Maso

On Sat, Jan 24, 2009 at 12:29 PM, Ghislain Fourny <http://x-query.com/mailman/listinfo/talk>wrote:

> Hello,
>
> Are you refering to C Omega? It is an interesting approach, thanks for
> pointing this out.
>
> What I am wondering is: how does it compare to start with
> object-orientation (here, C#) and add XML/Querying capabilities, versus to
> start with XML/XQuery and add object/item-orientation? In terms of
> expressiveness as well as performance?
>
> Kind regards,
> Ghislain Fourny
>
>   I think initially of Cu (.Net platform), a language that has XML,
>> relational, and OO structures all as first-class citizens.
>>
>>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://x-query.com/pipermail/talk/attachments/20090124/fd4fe45e/attachment.htm