From: Joe W. <jo...@gm...> - 2015-05-13 15:48:17
|
In that case, I'd suggest that you report it to su...@ox.... On Wed, May 13, 2015 at 11:07 AM, Loren Cahlander <lor...@gm... > wrote: > It was handling it until the release of 17 > > Sent from my iPhone > > On May 13, 2015, at 10:53 AM, Joe Wicentowski <jo...@gm...> wrote: > > You mean oXygen's highlighting of eXist's XQuery Update syntax? Yes, that > will be true as long as eXist doesn't match the spec. I wouldn't expect > oXygen to add special handling for eXist, though I certainly wouldn't > object to it! > > On Wed, May 13, 2015 at 10:33 AM, Loren Cahlander < > lor...@gm...> wrote: > >> I thought so. The syntax highlighting for XQuery update in oXygen 17 is >> broken. >> >> >> >> Sent from my iPad >> >> On May 13, 2015, at 9:53 AM, wol...@gm... wrote: >> >> Does eXist-db 2.2 support the XQuery 3.0 update syntax? >> Http://w3.org/TR/xquery-update-30 >> >> >> No, the xquery update features in eXist differ not only syntactically, >> but also conceptually from the W3C specification, which was published quite >> some time after eXist introduced the feature. We did not try to align the >> syntax as that would be confusing, but intentionally left it non-standard. >> >> Wolfgang >> >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development >> >> > |