Re: [basex-talk] eq vs =

Thank you Christian and Wray The implicit cast is the problem (as usual). I was expecting it to happen equally :( And I teach my students to use value comparisons when ever possible and to care about the cast yourself ;-) Yours Leo > On 13 Dec 2018, at 10:46, Christian Grün wrote: > > Hi

Re: [basex-talk] eq vs =

Hi Leo, The semantics of value comparisons (eq, ne, …) and general comparisons (=, !=, …) are different. As E. Wray indicated, sequences with more than one item can be compared with general comparisons; the result will always be a boolean (value comparisons will return an empty sequence if at

Re: [basex-talk] eq vs =

The value comparison operators (eq, lt, etc.) are designed for comparing single values (i.e. sequences of one value each). The general comparison operators (=, <, etc.) are designed for comparing sequences of more than one value. E. Wray Johnson > On Dec 13, 2018, at 4:16 AM, Leo Studer

[basex-talk] eq vs =

Hello Could someone explain me why this woks //country[@population = max(//@population)]/name Whereas this does not //country[@population eq max(//@population)]/name Thanks in advance Leo