Dear Michael,
thank you for reporting this.
The cited documentation page suggests that the Markup Blitz jar should be contained in the full distribution of BaseX 11.0, but it turns out that it is not. Sorry about that.
What you can do is get the jar of Markup Blitz 1.3 from Maven Centr
While testing some XQuery lookup expressions on BaseX 8.6.7, I got a wrong
result for this one:
(map{'a':(1,3)},map{'a':(2,4)})!?a[2]
It should have returned the second item of the 'a' entry for each of the maps,
i.e.
3 4
but it returns just
3
Apparently the predicate is ap
Hi Christian,
thank you for the quick fix! It now works fine with "latest".
Best regards
Gunther
> Gesendet: Freitag, 20. Januar 2017 um 09:50 Uhr
> Von: "Christian Grün"
> An: "Gunther Rademacher"
> Cc: BaseX
> Betreff: Re: [basex-talk]
Hello list,
I have a file some.xml containing
hello world!
and I can read it in BaseX code like this:
java org.basex.BaseX "declare namespace
fn='http://www.w3.org/2005/xpath-functions';fn:doc('some.xml')"
However I cannot use fn:unparsed-text() from a command line, when a
The order of attributes, including namespace declaration attributes, in
a direct element constructor is not significant. But while playing
around I found that it makes a difference with BaseX for expressions
that are embedded in an attribute.
So these two constructors produce different results
Uhr
Von: "Andy Bunce"
An: "Gunther Rademacher"
Cc: "Christian Grün" , "basex-talk@mailman.uni-konstanz.de"
Betreff: Re: [basex-talk] Problem deleting jar packaged item from repo
Hi Gunther,
Thanks for the 5.39 update.
It is not how to set the namesp
uot;
An: "Christian Grün"
Cc: "Gunther Rademacher" , "basex-talk@mailman.uni-konstanz.de"
Betreff: Re: Re: [basex-talk] Problem deleting jar packaged item from repo
Hi Gunther Christian,
>Will take care of this.
Thanks that's great. I have added the c
. April 2016 um 11:34 Uhr
Von: "Andy Bunce"
An: "Gunther Rademacher"
Cc: "Christian Grün" , "basex-talk@mailman.uni-konstanz.de"
Betreff: Re: [basex-talk] Problem deleting jar packaged item from repo
Hi,
I want a solution that lives in the reposit
noticed that this is not enforced, though.
Best regards
Gunther
Gesendet: Freitag, 08. April 2016 um 08:55 Uhr
Von: "Christian Grün"
An: "Gunther Rademacher"
Cc: "Andy Bunce" , "basex-talk@mailman.uni-konstanz.de"
Betreff: Re: Re: [basex-talk]
6 um 08:55 Uhr
Von: "Christian Grün"
An: "Gunther Rademacher"
Cc: "Andy Bunce" , "basex-talk@mailman.uni-konstanz.de"
Betreff: Re: Re: [basex-talk] Problem deleting jar packaged item from repo
Hi Gunther,
I agree, it wouldn’t make too much sense to add a d
g "declare namespace " or just an EQName literal instead. I have put my extension function class files into the classpath for checking this.
Am I missing something here?
Best regards
Gunther
Gesendet: Donnerstag, 07. April 2016 um 19:34 Uhr
Von: "Christian Grün"
36 Uhr
Von: "Christian Grün"
An: "Gunther Rademacher"
Cc: BaseX
Betreff: Re: [basex-talk] BaseX optimizer performance on REx-generated parser
Hi Gunther,
Your code looks excellent. And I was amazed to see you’ve even found
out how to build the error node via our MemBuilder
The modified code is attached to this mail. It is stripped down to what
would be added to REx-generated code for '-basex'.
Best regards
Gunther
Gesendet: Freitag, 01. April 2016 um 17:57 Uhr
Von: "Christian Grün"
An: "Gunther Rademacher"
Cc: BaseX
Betreff: Re: [base
poses:
>
> - adapting to the extension function API (necessary when using Saxon-HE)
> - using Saxon's native tree builder.
>
> Best regards
> Gunther
> --
>
>
> Gesendet: Donnerstag, 31. März 2016 um 11:14 Uhr
> Von: "Christian Grün"
> An: &qu
)
- using Saxon's native tree builder.
Best regards
Gunther
--
Gesendet: Donnerstag, 31. März 2016 um 11:14 Uhr
Von: "Christian Grün"
An: "Gunther Rademacher"
Cc: BaseX
Betreff: Re: Re: [basex-talk] BaseX optimizer performance on REx-generated
parser
Hi Gu
Hi Christian,
> This sounds interesting indeed! Could you provide us with a link to
> the Saxon extension functions?
it's an option when generating a parser in Java on the REx website, http://bottlecaps.de/rex/
For parsing XQuery from XQuery via a Saxon extension function,
- d
Hi Christian,
thank you for your analysis. Here is my view of this:
- generally I would second your preference for typed code. It feels
cleaner to me, and that's why the type specifications were there
originally.
- tail call optimization is crucial for REx generated code. It is
Hi Andy,
that's correct. p:transition ought to be tail-call optimized to be
prepared for tokens of arbitrary size.
Best regards
Gunther
On 29.03.2016 19:17, Andy Bunce wrote:
Hi Gunther,
Do I under understand correctly from:
https://twitter.com/__Gunther__/status/709744679361912832
Given t
Hi,
in a recent update of REx parser generator (v5.37), some type
specifications were removed from generated XQuery and XSLT functions.
This affects tail-recursive functions, and it was done because it turned
out that MarkLogic fails to optimize tail calls, presumably due to an
explicit type
As explained in
http://www.w3.org/TR/xquery-operators/#func-subtract-dates
the implicit timezone should be used for augmenting an xs:date without a
timezone before subtracting it from one with a timezone.
BaseX however appears to be using timezone Z in this case.
The following xquery demo
20 matches
Mail list logo
