Re: [basex-talk] Failure with comment in editor when commenting out a regex

2018-08-01 Thread Christian Grün
> > Aehm, no, that is still part of the regular expression. This does not apply anymore if you insert (: before the quotes. As Liam wrote, the regex won’t be parsed anymore in that case.

[basex-talk] Failure with comment in editor when commenting out a regex

2018-08-01 Thread Andreas Mixich
Hi Christian, you wrote:> I’m being presented with the following error message: > > [XPST0003] Invalid value, simple expression expected. Me too, if I just copy and paste the code I have sent. See, attached, a simple module, that produces the error I named first. > The error message is

Re: [basex-talk] Failure with comment in editor when commenting out a regex

2018-08-01 Thread Liam R. E. Quin
On Wed, 2018-08-01 at 22:31 +0200, Andreas Mixich wrote: > host :) > > Editor/GUI warns, that: "no expression allowed in library module" and > places error marker at the two slashes // after the :)( in the regex. Well, it's right - since it's in a comment it's not in a regex, it's just :) in a

Re: [basex-talk] Failure with comment in editor when commenting out a regex

2018-08-01 Thread Christian Grün
> Editor/GUI warns, that: "no expression allowed in library module" and > places error marker at the two slashes // after the :)( in the regex. I’m being presented with the following error message: [XPST0003] Invalid value, simple expression expected. The error message is correct, because your

[basex-talk] Failure with comment in editor when commenting out a regex

2018-08-01 Thread Andreas Mixich
Hi, it may be already known, that the editor seems to hick up with the parsing, when it comes around some strange combinations of chars within the comment. I just came around this: (: let $str := "http://foo.bar/barz/index.html?bla=2; let $str2 :=