Re: [NTG-context] xml expression error

2016-05-12 Thread Hans Hagen 

On 5/12/2016 1:49 PM, Meer, Hans van der wrote:

I think I have the problem nailed down to the fact that in the comparison:
something >= -1234
the parser in question separates the minus in the negative number into a
separate child node, apart from the digits; witness the errormessage in
the log below.
Changing the number  -1234 in the arithmetic expression
tonumber("-1234") (mind the quotes) does give a correctly evaluated
expression.

Still, I am baffled by the fact that in arithmetic expressions positive
and negative numbers are treated differently in the filtering operation.


it's more that 'names' are intercepted .. can you test (lxml-lpt.lua) 
with:


local lp_child   = Cc("expr.child(ll,'") * R("az","AZ") * 
R("az","AZ","--","__")^0 * Cc("')")


Hans


Hans van der Meer



On 29 Apr 2016, at 15:04, Meer, Hans van der > wrote:

Here is a minimal example showing that even a number as -1 is not
correctly handled by the lpath[selection]-code.
I really am convinced that not handling negative numbers should
qualify as a mistake.

Hans van der Meer


% failure of negative number comparison.
\startxmlsetups demo:numberfail
\xmlsetsetup{#1}{root|node}{demo:numberfail:*}
\stopxmlsetups
\xmlregisterdocumentsetup{demo}{demo:numberfail}
\startxmlsetups demo:numberfail:root
@atta >= 1:\crlf
\xmlfilter{#1}{/[number(@atta) >= 1]/command(demo:numberfail:node)}
\blank
@atta >= -1:\crlf
\xmlfilter{#1}{/[number(@atta) >= -1]/command(demo:numberfail:node)}
\xmlfilter{#1}{/[number(@atta) >=
number(-1)]/command(demo:numberfail:node)}
\stopxmlsetups
\startxmlsetups demo:numberfail:node
node: attribute atta = \xmlatt{#1}{atta}\crlf
\stopxmlsetups
\startbuffer[numberfail]




\stopbuffer
\starttext
\xmlprocessbuffer{demo}{numberfail}{}
the error from \type{\xmlfilter{#1}{/[number(@atta) >=
-1]/command(demo:numberfail:node)}}:
\starttyping
xml > lpath > error in expression: number(@atta) >= -1 =>
expr.number((ll.at  and ll.at ['atta']))
>= expr.child(ll,'-')1
\stoptyping

the error from \type{\xmlfilter{#1}{/[number(@atta) >=
number(-1)]/command(demo:numberfail:node)}}:
\starttyping
xml > lpath > error in expression: number(@atta) >= number(-1) =>
expr.number((ll.at  and ll.at ['atta']))
>= expr.number(expr.child(ll,'-')1)
\stoptyping
\stoptext



___




___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___




--

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] xml expression error

2016-05-12 Thread Meer, Hans van der 
I think I have the problem nailed down to the fact that in the comparison:
something >= -1234
the parser in question separates the minus in the negative number into a 
separate child node, apart from the digits; witness the errormessage in the log 
below.
Changing the number  -1234 in the arithmetic expression to number("-1234") 
(mind the quotes) does give a correctly evaluated expression.

Still, I am baffled by the fact that in arithmetic expressions positive and 
negative numbers are treated differently in the filtering operation.

Hans van der Meer


On 29 Apr 2016, at 15:04, Meer, Hans van der 
> wrote:

Here is a minimal example showing that even a number as -1 is not correctly 
handled by the lpath[selection]-code.
I really am convinced that not handling negative numbers should qualify as a 
mistake.

Hans van der Meer


% failure of negative number comparison.
\startxmlsetups demo:numberfail
\xmlsetsetup{#1}{root|node}{demo:numberfail:*}
\stopxmlsetups
\xmlregisterdocumentsetup{demo}{demo:numberfail}
\startxmlsetups demo:numberfail:root
@atta >= 1:\crlf
\xmlfilter{#1}{/[number(@atta) >= 1]/command(demo:numberfail:node)}
\blank
@atta >= -1:\crlf
\xmlfilter{#1}{/[number(@atta) >= -1]/command(demo:numberfail:node)}
\xmlfilter{#1}{/[number(@atta) >= number(-1)]/command(demo:numberfail:node)}
\stopxmlsetups
\startxmlsetups demo:numberfail:node
node: attribute atta = \xmlatt{#1}{atta}\crlf
\stopxmlsetups
\startbuffer[numberfail]




\stopbuffer
\starttext
\xmlprocessbuffer{demo}{numberfail}{}
the error from \type{\xmlfilter{#1}{/[number(@atta) >= 
-1]/command(demo:numberfail:node)}}:
\starttyping
xml > lpath > error in expression: number(@atta) >= -1 => 
expr.number((ll.at and ll.at['atta'])) >= 
expr.child(ll,'-')1
\stoptyping

the error from \type{\xmlfilter{#1}{/[number(@atta) >= 
number(-1)]/command(demo:numberfail:node)}}:
\starttyping
xml > lpath > error in expression: number(@atta) >= number(-1) => 
expr.number((ll.at and ll.at['atta'])) >= 
expr.number(expr.child(ll,'-')1)
\stoptyping
\stoptext

___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] xml expression error

2016-04-29 Thread Meer, Hans van der 

On 28 Apr 2016, at 22:13, Pablo Rodriguez > 
wrote:

On 04/28/2016 05:06 PM, dr. Hans van der Meer wrote:
Why is there anexpression error here? I would expect that the expression
number(-1101) evaluates to a negative number taking part in the
comparsion. It looks as if the minus sign is not seen as an unary minus,
while -1101 should have be evaluated by Lua's tonumber(-1101).

relevant code snippet is:
\xmlfilter{#1}{lpath[number(@date) <= number(-1101)]/command(...)

I wouldn’t get it, even with a minimal sample, but xml-mkiv.pdf includes
the shortcut for this function.

Here is a minimal example showing that even a number as -1 is not correctly 
handled by the lpath[selection]-code.
I really am convinced that not handling negative numbers should qualify as a 
mistake.

Hans van der Meer


% failure of negative number comparison.
\startxmlsetups demo:numberfail
\xmlsetsetup{#1}{root|node}{demo:numberfail:*}
\stopxmlsetups
\xmlregisterdocumentsetup{demo}{demo:numberfail}
\startxmlsetups demo:numberfail:root
@atta >= 1:\crlf
\xmlfilter{#1}{/[number(@atta) >= 1]/command(demo:numberfail:node)}
\blank
@atta >= -1:\crlf
\xmlfilter{#1}{/[number(@atta) >= -1]/command(demo:numberfail:node)}
\xmlfilter{#1}{/[number(@atta) >= number(-1)]/command(demo:numberfail:node)}
\stopxmlsetups
\startxmlsetups demo:numberfail:node
node: attribute atta = \xmlatt{#1}{atta}\crlf
\stopxmlsetups
\startbuffer[numberfail]




\stopbuffer
\starttext
\xmlprocessbuffer{demo}{numberfail}{}
the error from \type{\xmlfilter{#1}{/[number(@atta) >= 
-1]/command(demo:numberfail:node)}}:
\starttyping
xml > lpath > error in expression: number(@atta) >= -1 => 
expr.number((ll.at and ll.at['atta'])) >= 
expr.child(ll,'-')1
\stoptyping

the error from \type{\xmlfilter{#1}{/[number(@atta) >= 
number(-1)]/command(demo:numberfail:node)}}:
\starttyping
xml > lpath > error in expression: number(@atta) >= number(-1) => 
expr.number((ll.at and ll.at['atta'])) >= 
expr.number(expr.child(ll,'-')1)
\stoptyping
\stoptext




xml-number.pdf
Description: xml-number.pdf
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] xml expression error

2016-04-28 Thread Meer, Hans van der 

> On 28 Apr 2016, at 22:13, Pablo Rodriguez  wrote:
> 
> On 04/28/2016 05:06 PM, dr. Hans van der Meer wrote:
>> Why is there anexpression error here? I would expect that the expression
>> number(-1101) evaluates to a negative number taking part in the
>> comparsion. It looks as if the minus sign is not seen as an unary minus,
>> while -1101 should have be evaluated by Lua's tonumber(-1101).
>> 
>> relevant code snippet is:
>> \xmlfilter{#1}{lpath[number(@date) <= number(-1101)]/command(...)
> 
> Sorry, Hans, I guess my question will be stupid, but why don’t use
> "tonumber(-1101)"?

It is convenient to use positive numbers for dates after the year 0: AD = Anno 
Domine,
and negative numbers for years before: BC = Before Christ.
Comparing dates is easy in both eras.

> 
> I wouldn’t get it, even with a minimal sample, but xml-mkiv.pdf includes
> the shortcut for this function.
> 
> Just in case it might even help ;-),

Has to wait until tomorrow, because it is already late in the evening.

Hans van der Meer




___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] xml expression error

2016-04-28 Thread Pablo Rodriguez 
On 04/28/2016 05:06 PM, dr. Hans van der Meer wrote:
> Why is there anexpression error here? I would expect that the expression
> number(-1101) evaluates to a negative number taking part in the
> comparsion. It looks as if the minus sign is not seen as an unary minus,
> while -1101 should have be evaluated by Lua's tonumber(-1101).
> 
> relevant code snippet is:
> \xmlfilter{#1}{lpath[number(@date) <= number(-1101)]/command(...)

Sorry, Hans, I guess my question will be stupid, but why don’t use
"tonumber(-1101)"?

I wouldn’t get it, even with a minimal sample, but xml-mkiv.pdf includes
the shortcut for this function.

Just in case it might even help ;-),

Pablo
-- 
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] xml expression error

2016-04-28 Thread dr. Hans van der Meer 
Why is there anexpression error here? I would expect that the expression 
number(-1101) evaluates to a negative number taking part in the comparsion. 
It looks as if the minus sign is not seen as an unary minus, while -1101 
should have be evaluated by Lua's tonumber(-1101).

relevant code snippet is:
\xmlfilter{#1}{lpath[number(@date) <= number(-1101)]/command(...)

xml > lpath > error in expression: number(@date) <= number(-1101) => 
expr.number((ll.at and ll.at['date'])) <= 
expr.number(expr.child(ll,'-')1101)

Changing number(-1101) to -1101 does not make a difference. 
The @date attribute has no problem with a negative value.

Hans van der Meer

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___