Hi Christan,

 

I already have reduced the code significantly. I can give it another go.

 

In the meanwhile please not parameter: “$element.content”  in the function: “$go”.

Nowhere in the function is the parameter reassigned another value, yet the value is changed at the “content2”-trace.

 

- Rob

 

Van: Christian Grün [mailto:christian.gruen@gmail.com]
Verzonden: vrijdag 7 november 2014 18:04
Aan: Rob Stapper
CC: BaseX
Onderwerp: Re: [basex-talk] unexpected behaviour

 

Hi Rob,

 

thanks for the example code. Could you possibly reduce it to a shorter snippet that still demonstrates the surprising behavior?

 

Best,

Christian

 

 

On Fri, Nov 7, 2014 at 6:00 PM, Rob Stapper <r.stapper@lijbrandt.nl> wrote:

Hi,

 

Running the attached program produces the next evaluation.

 

Evaluating:

- elementSeq: <A ref="var1"><B><X1/></B></A>

- content0: <X1/>

- content2: <X1/>

- elementSeq: <A ref="var1"><B><X2/></B></A>

- content0: <X2/>

- content2: <X1/>

 

I can’t explain the value of the last “- content2: ”-trace.

I expect it to be the same value as the last “- content0: ”-trace.

 

What’s happening here?

 

- Rob Stapper

 

 

Afbeelding verwijderd door afzender.

Dit e-mailbericht bevat geen virussen en malware omdat avast! Antivirus actief is.

 

 



Dit e-mailbericht bevat geen virussen en malware omdat avast! Antivirus actief is.