intersection variable holds result correctly only once

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

intersection variable holds result correctly only once

Stefan Wachter
Hi all,

I encountered a problem in a rather complicated setup. It seems that a
variable containing an intersection delivers its value correctly only
once. Unfortunately I could not extract the gist in a simple example.
Here is my setup:

I have a stylesheet that accumulates log messages by their message text
and the "area" in which they occurred. The input to the stylesheet is a
file containing all log messages together with their line numbers. I
created two keys: one for accessing the log messages by their message
text and the other for accessing the log messages by their "area". (By
"area" I mean that certain log messages of certain line numbers belong
to the same area of interest.)

The log messages are accumulated by giving an overview line for each
area summing the total number of log messages for that area and for each
log message text that occurred in that area how often it occurred. Here
is the relevant part of the stylesheet:

  <xsl:template match="log">
    <xsl:variable name="lnr" select="vdp:lnr(.)"/>
    <xsl:variable name="logsOfArea" select="key('lnr', $lnr)"/>
    <xsl:variable name="logsOfMsg" select="key('messages', .)"/>
    <xsl:variable name="logsOfAreaMsg" select="$logsOfArea intersect
$logsOfMsg"/>
    <xsl:if  test="$lnr and not(some $x in $logsOfArea satisfies $x
&lt;&lt; .)">
      <!-- overview line -->
      <xsl:copy>
        <xsl:copy-of select="@*"/>
        <xsl:attribute name="herkunft" select="vdp:herkunft(.)"/>
        <xsl:attribute name="lnr" select="$lnr"/>
        <xsl:attribute name="level" select="'error'"/>
        <xsl:text/>Leitziffer hat <xsl:value-of
select="count($logsOfArea)"/> Validierungsfehler<xsl:text/>
      </xsl:copy>
    </xsl:if>
    <xsl:if test="not(some $x in $logsOfAreaMsg satisfies $x &lt;&lt; .)">
      <!-- line counting the number of occurrences of a message in an
area -->
      <xsl:copy>
        <xsl:copy-of select="@*"/>
        <xsl:attribute name="herkunft" select="vdp:herkunft(.)"/>
        <xsl:attribute name="lnr" select="$lnr"/>
        <xsl:attribute name="level" select="'anmerkung'"/>
<!-- problematic line follows -->
        <xsl:value-of select="count($logsOfArea intersect
$logsOfMsg)"/>mal: <xsl:text/>
        <xsl:copy-of select="node()"/>
      </xsl:copy>
      <xsl:text>&#10;</xsl:text>
    </xsl:if>
  </xsl:template>
     
When I replace the intersect expression in the problematic line by a
variable that already holds that intersection

        <xsl:value-of select="count($logsOfLzMsg)"/>mal: <xsl:text/>

the result is wrong.

The result without using the intersection variable is:

Leitziffer hat 117 Validierungsfehler

26mal: The content of element type "ebene_para_frei" must match
"(titel?,fundstelle?,inhalt?,vorbemerkung_para?,((absatz|absatz_auslassung|absatz_entfallen)+|(para_frei+|art_frei+)|ebenen_para_frei)?)".


62mal: The content of element type "absch" is incomplete, it must match
"(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschnitte?)|abschnitte))".


24mal: The content of element type "absch" must match
"(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschnitte?)|abschnitte))".

1mal: The content of element type "hoch" must match "null".

2mal: The content of element type "li_o" is incomplete, it must match
"(p|ul|ol|grafik|table)+".

2mal: The content of element type "vorbemerkung_para" is incomplete, it
must match
"(titel?,(((p|ul|ol|grafik|table)+,(para*|art*))|(para+|art+)))".


The result using the intersection variable is:

Leitziffer hat 117 Validierungsfehler

50mal: The content of element type "ebene_para_frei" must match
"(titel?,fundstelle?,inhalt?,vorbemerkung_para?,((absatz|absatz_auslassung|absatz_entfallen)+|(para_frei+|art_frei+)|ebenen_para_frei)?)".


62mal: The content of element type "absch" is incomplete, it must match
"(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschnitte?)|abschnitte))".


50mal: The content of element type "absch" must match
"(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschnitte?)|abschnitte))".


1mal: The content of element type "hoch" must match "null".

2mal: The content of element type "li_o" is incomplete, it must match
"(p|ul|ol|grafik|table)+".

2mal: The content of element type "vorbemerkung_para" is incomplete, it
must match "(titel?,(((p|ul|ol|grafik|table)+,(para*|art*))|(para+|art+)))".

Clearly, the overview line is still correct, but the first and third
line counting the number of occurrences of a specific message are
incorrect (reporting 50 occurences instead of 26 and 24, respectively).

I am sorry that I could not find a more succinct example demonstrating
the problem.

Regards,
--Stefan




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

RE: intersection variable holds result correctly only once

Michael Kay
I can speculate as to what's going wrong here: Saxon tries to analyze at
compile time whether a variable is only used once, and if so it effectively
evaluates it on demand and discards the value immediately. The most likely
explanation is that this analysis has gone wrong, and a variable has been
classified wrongly as a "use once" variable. I might be able to confirm this
if you add

saxon:explain="yes" xmlns:saxon="http://saxon.sf.net/"

to the containing xsl:template, and show me the output.

If you can put together a set of files that allow me to reproduce the
problem (even if it's complex) I'd appreciate it as it's going to be
difficult to fix the bug otherwise.

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of
> Stefan Wachter
> Sent: 17 February 2006 08:28
> To: [hidden email]
> Subject: [saxon] intersection variable holds result correctly
> only once
>
> Hi all,
>
> I encountered a problem in a rather complicated setup. It
> seems that a
> variable containing an intersection delivers its value correctly only
> once. Unfortunately I could not extract the gist in a simple example.
> Here is my setup:
>
> I have a stylesheet that accumulates log messages by their
> message text
> and the "area" in which they occurred. The input to the
> stylesheet is a
> file containing all log messages together with their line numbers. I
> created two keys: one for accessing the log messages by their message
> text and the other for accessing the log messages by their
> "area". (By
> "area" I mean that certain log messages of certain line
> numbers belong
> to the same area of interest.)
>
> The log messages are accumulated by giving an overview line for each
> area summing the total number of log messages for that area
> and for each
> log message text that occurred in that area how often it
> occurred. Here
> is the relevant part of the stylesheet:
>
>   <xsl:template match="log">
>     <xsl:variable name="lnr" select="vdp:lnr(.)"/>
>     <xsl:variable name="logsOfArea" select="key('lnr', $lnr)"/>
>     <xsl:variable name="logsOfMsg" select="key('messages', .)"/>
>     <xsl:variable name="logsOfAreaMsg" select="$logsOfArea intersect
> $logsOfMsg"/>
>     <xsl:if  test="$lnr and not(some $x in $logsOfArea satisfies $x
> &lt;&lt; .)">
>       <!-- overview line -->
>       <xsl:copy>
>         <xsl:copy-of select="@*"/>
>         <xsl:attribute name="herkunft" select="vdp:herkunft(.)"/>
>         <xsl:attribute name="lnr" select="$lnr"/>
>         <xsl:attribute name="level" select="'error'"/>
>         <xsl:text/>Leitziffer hat <xsl:value-of
> select="count($logsOfArea)"/> Validierungsfehler<xsl:text/>
>       </xsl:copy>
>     </xsl:if>
>     <xsl:if test="not(some $x in $logsOfAreaMsg satisfies $x
> &lt;&lt; .)">
>       <!-- line counting the number of occurrences of a message in an
> area -->
>       <xsl:copy>
>         <xsl:copy-of select="@*"/>
>         <xsl:attribute name="herkunft" select="vdp:herkunft(.)"/>
>         <xsl:attribute name="lnr" select="$lnr"/>
>         <xsl:attribute name="level" select="'anmerkung'"/>
> <!-- problematic line follows -->
>         <xsl:value-of select="count($logsOfArea intersect
> $logsOfMsg)"/>mal: <xsl:text/>
>         <xsl:copy-of select="node()"/>
>       </xsl:copy>
>       <xsl:text>&#10;</xsl:text>
>     </xsl:if>
>   </xsl:template>
>      
> When I replace the intersect expression in the problematic line by a
> variable that already holds that intersection
>
>         <xsl:value-of select="count($logsOfLzMsg)"/>mal: <xsl:text/>
>
> the result is wrong.
>
> The result without using the intersection variable is:
>
> Leitziffer hat 117 Validierungsfehler
>
> 26mal: The content of element type "ebene_para_frei" must match
> "(titel?,fundstelle?,inhalt?,vorbemerkung_para?,((absatz|absat
> z_auslassung|absatz_entfallen)+|(para_frei+|art_frei+)|ebenen_
> para_frei)?)".
>
>
> 62mal: The content of element type "absch" is incomplete, it
> must match
> "(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschni
> tte?)|abschnitte))".
>
>
> 24mal: The content of element type "absch" must match
> "(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschni
> tte?)|abschnitte))".
>
> 1mal: The content of element type "hoch" must match "null".
>
> 2mal: The content of element type "li_o" is incomplete, it must match
> "(p|ul|ol|grafik|table)+".
>
> 2mal: The content of element type "vorbemerkung_para" is
> incomplete, it
> must match
> "(titel?,(((p|ul|ol|grafik|table)+,(para*|art*))|(para+|art+)))".
>
>
> The result using the intersection variable is:
>
> Leitziffer hat 117 Validierungsfehler
>
> 50mal: The content of element type "ebene_para_frei" must match
> "(titel?,fundstelle?,inhalt?,vorbemerkung_para?,((absatz|absat
> z_auslassung|absatz_entfallen)+|(para_frei+|art_frei+)|ebenen_
> para_frei)?)".
>
>
> 62mal: The content of element type "absch" is incomplete, it
> must match
> "(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschni
> tte?)|abschnitte))".
>
>
> 50mal: The content of element type "absch" must match
> "(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschni
> tte?)|abschnitte))".
>
>
> 1mal: The content of element type "hoch" must match "null".
>
> 2mal: The content of element type "li_o" is incomplete, it must match
> "(p|ul|ol|grafik|table)+".
>
> 2mal: The content of element type "vorbemerkung_para" is
> incomplete, it
> must match
> "(titel?,(((p|ul|ol|grafik|table)+,(para*|art*))|(para+|art+)))".
>
> Clearly, the overview line is still correct, but the first and third
> line counting the number of occurrences of a specific message are
> incorrect (reporting 50 occurences instead of 26 and 24,
> respectively).
>
> I am sorry that I could not find a more succinct example
> demonstrating
> the problem.
>
> Regards,
> --Stefan
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  
> DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&
> dat=121642
> _______________________________________________
> saxon-help mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help
>




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

RE: intersection variable holds result correctly only once

Rademacher, Gunther
In reply to this post by Stefan Wachter
The incorrect count value of 50 reminds me of my experience with this
bug:

https://sourceforge.net/tracker/index.php?func=detail&aid=1395196&group_
id=29872&atid=397617

Could this be another occurrence?


-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Stefan
Wachter
Sent: Friday, February 17, 2006 9:28 AM
To: [hidden email]
Subject: [saxon] intersection variable holds result correctly only once

...
> Clearly, the overview line is still correct, but the first and third
> line counting the number of occurrences of a specific message are
> incorrect (reporting 50 occurences instead of 26 and 24,
respectively).
...


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
<a href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642">http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help
Reply | Threaded
Open this post in threaded view
|

Re: intersection variable holds result correctly only once

Stefan Wachter
In reply to this post by Michael Kay
Hello Mr. Kay,

attached you find the stylesheet (akkumuliere-validierung.xsl) its input
(tmp-log-s-be_validate.xml) and a file (herkunft.xml) whose absolute
filename must be specified as a parameter named "herkunftFilePath".
Below is the output when running the transformation with explain="yes".
I hope this information helps you.

Regards,
--Stefan


     [java]                     let $lnr[refCount=44] :=
     [java]                       function vdp:lnr
     [java]                         .
     [java]                     return
     [java]                       if
     [java]                         $lnr
     [java]                       then
     [java]                         let $logsOfArea[refCount=33] :=
     [java]                           function key
     [java]                             "lnr"
     [java]                             atomize
     [java]                               $lnr
     [java]                             /
     [java]                         return
     [java]                           let $logsOfMsg[refCount=11] :=
     [java]                             function key
     [java]                               "messages"
     [java]                               atomize
     [java]                                 .
     [java]                               /
     [java]                           return
     [java]                             let $logsOfAreaMsg[refCount=22] :=
     [java]                               operator intersect
     [java]                                 $logsOfArea
     [java]                                 $logsOfMsg
     [java]                             return
     [java]                                   if
     [java]                                     function not
     [java]                                       let
$zz:8984226[refCount=20] :=
     [java]                                         lazy
     [java]                                           .
     [java]                                       return
     [java]                                         some $x in
     [java]                                           $logsOfArea
     [java]                                         satisfies
     [java]                                           operator <<
     [java]                                             $x
     [java]                                             $zz:8984226
     [java]                                   then
     [java]                                     copy
     [java]                                   if
     [java]                                     function not
     [java]                                       let
$zz:2943240[refCount=20] :=
     [java]                                         lazy
     [java]                                           .
     [java]                                       return
     [java]                                         some $x in
     [java]                                           $logsOfAreaMsg
     [java]                                         satisfies
     [java]                                           operator <<
     [java]                                             $x
     [java]                                             $zz:2943240
     [java]                                   then
     [java]                                         copy
     [java]                                         value-of
     [java]                                           "
     [java] "
     [java]                       else if
     [java]                         true()
     [java]                       then
     [java]                         copyOf validation=skip
     [java]                           .




Michael Kay wrote:

> I can speculate as to what's going wrong here: Saxon tries to analyze at
> compile time whether a variable is only used once, and if so it effectively
> evaluates it on demand and discards the value immediately. The most likely
> explanation is that this analysis has gone wrong, and a variable has been
> classified wrongly as a "use once" variable. I might be able to confirm this
> if you add
>
> saxon:explain="yes" xmlns:saxon="http://saxon.sf.net/"
>
> to the containing xsl:template, and show me the output.
>
> If you can put together a set of files that allow me to reproduce the
> problem (even if it's complex) I'd appreciate it as it's going to be
> difficult to fix the bug otherwise.
>
> Michael Kay
> http://www.saxonica.com/
>  
>
>  
>> -----Original Message-----
>> From: [hidden email]
>> [mailto:[hidden email]] On Behalf Of
>> Stefan Wachter
>> Sent: 17 February 2006 08:28
>> To: [hidden email]
>> Subject: [saxon] intersection variable holds result correctly
>> only once
>>
>> Hi all,
>>
>> I encountered a problem in a rather complicated setup. It
>> seems that a
>> variable containing an intersection delivers its value correctly only
>> once. Unfortunately I could not extract the gist in a simple example.
>> Here is my setup:
>>
>> I have a stylesheet that accumulates log messages by their
>> message text
>> and the "area" in which they occurred. The input to the
>> stylesheet is a
>> file containing all log messages together with their line numbers. I
>> created two keys: one for accessing the log messages by their message
>> text and the other for accessing the log messages by their
>> "area". (By
>> "area" I mean that certain log messages of certain line
>> numbers belong
>> to the same area of interest.)
>>
>> The log messages are accumulated by giving an overview line for each
>> area summing the total number of log messages for that area
>> and for each
>> log message text that occurred in that area how often it
>> occurred. Here
>> is the relevant part of the stylesheet:
>>
>>   <xsl:template match="log">
>>     <xsl:variable name="lnr" select="vdp:lnr(.)"/>
>>     <xsl:variable name="logsOfArea" select="key('lnr', $lnr)"/>
>>     <xsl:variable name="logsOfMsg" select="key('messages', .)"/>
>>     <xsl:variable name="logsOfAreaMsg" select="$logsOfArea intersect
>> $logsOfMsg"/>
>>     <xsl:if  test="$lnr and not(some $x in $logsOfArea satisfies $x
>> &lt;&lt; .)">
>>       <!-- overview line -->
>>       <xsl:copy>
>>         <xsl:copy-of select="@*"/>
>>         <xsl:attribute name="herkunft" select="vdp:herkunft(.)"/>
>>         <xsl:attribute name="lnr" select="$lnr"/>
>>         <xsl:attribute name="level" select="'error'"/>
>>         <xsl:text/>Leitziffer hat <xsl:value-of
>> select="count($logsOfArea)"/> Validierungsfehler<xsl:text/>
>>       </xsl:copy>
>>     </xsl:if>
>>     <xsl:if test="not(some $x in $logsOfAreaMsg satisfies $x
>> &lt;&lt; .)">
>>       <!-- line counting the number of occurrences of a message in an
>> area -->
>>       <xsl:copy>
>>         <xsl:copy-of select="@*"/>
>>         <xsl:attribute name="herkunft" select="vdp:herkunft(.)"/>
>>         <xsl:attribute name="lnr" select="$lnr"/>
>>         <xsl:attribute name="level" select="'anmerkung'"/>
>> <!-- problematic line follows -->
>>         <xsl:value-of select="count($logsOfArea intersect
>> $logsOfMsg)"/>mal: <xsl:text/>
>>         <xsl:copy-of select="node()"/>
>>       </xsl:copy>
>>       <xsl:text>&#10;</xsl:text>
>>     </xsl:if>
>>   </xsl:template>
>>      
>> When I replace the intersect expression in the problematic line by a
>> variable that already holds that intersection
>>
>>         <xsl:value-of select="count($logsOfLzMsg)"/>mal: <xsl:text/>
>>
>> the result is wrong.
>>
>> The result without using the intersection variable is:
>>
>> Leitziffer hat 117 Validierungsfehler
>>
>> 26mal: The content of element type "ebene_para_frei" must match
>> "(titel?,fundstelle?,inhalt?,vorbemerkung_para?,((absatz|absat
>> z_auslassung|absatz_entfallen)+|(para_frei+|art_frei+)|ebenen_
>> para_frei)?)".
>>
>>
>> 62mal: The content of element type "absch" is incomplete, it
>> must match
>> "(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschni
>> tte?)|abschnitte))".
>>
>>
>> 24mal: The content of element type "absch" must match
>> "(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschni
>> tte?)|abschnitte))".
>>
>> 1mal: The content of element type "hoch" must match "null".
>>
>> 2mal: The content of element type "li_o" is incomplete, it must match
>> "(p|ul|ol|grafik|table)+".
>>
>> 2mal: The content of element type "vorbemerkung_para" is
>> incomplete, it
>> must match
>> "(titel?,(((p|ul|ol|grafik|table)+,(para*|art*))|(para+|art+)))".
>>
>>
>> The result using the intersection variable is:
>>
>> Leitziffer hat 117 Validierungsfehler
>>
>> 50mal: The content of element type "ebene_para_frei" must match
>> "(titel?,fundstelle?,inhalt?,vorbemerkung_para?,((absatz|absat
>> z_auslassung|absatz_entfallen)+|(para_frei+|art_frei+)|ebenen_
>> para_frei)?)".
>>
>>
>> 62mal: The content of element type "absch" is incomplete, it
>> must match
>> "(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschni
>> tte?)|abschnitte))".
>>
>>
>> 50mal: The content of element type "absch" must match
>> "(titel?,vorbemerkung_absch?,(((p|ul|ol|grafik|table)+,abschni
>> tte?)|abschnitte))".
>>
>>
>> 1mal: The content of element type "hoch" must match "null".
>>
>> 2mal: The content of element type "li_o" is incomplete, it must match
>> "(p|ul|ol|grafik|table)+".
>>
>> 2mal: The content of element type "vorbemerkung_para" is
>> incomplete, it
>> must match
>> "(titel?,(((p|ul|ol|grafik|table)+,(para*|art*))|(para+|art+)))".
>>
>> Clearly, the overview line is still correct, but the first and third
>> line counting the number of occurrences of a specific message are
>> incorrect (reporting 50 occurences instead of 26 and 24,
>> respectively).
>>
>> I am sorry that I could not find a more succinct example
>> demonstrating
>> the problem.
>>
>> Regards,
>> --Stefan
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc. Do you grep
>> through log files
>> for problems?  Stop!  Download the new AJAX search engine that makes
>> searching your log files as easy as surfing the  web.  
>> DOWNLOAD SPLUNK!
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&
>> dat=121642
>> _______________________________________________
>> saxon-help mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/saxon-help
>>
>>    
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> saxon-help mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help
>
>
>  


tmp.tar.bz2 (18K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: intersection variable holds result correctly only once

Michael Kay
In reply to this post by Rademacher, Gunther

Thanks Gunther, I think you're absolutely right. I didn't spot the
similarity, but it definitely shows all the right symptoms.

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of
> Rademacher, Gunther
> Sent: 17 February 2006 15:05
> To: [hidden email]
> Subject: RE: [saxon] intersection variable holds result
> correctly only once
>
> The incorrect count value of 50 reminds me of my experience with this
> bug:
>
> https://sourceforge.net/tracker/index.php?func=detail&aid=1395
> 196&group_
> id=29872&atid=397617
>
> Could this be another occurrence?
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Stefan
> Wachter
> Sent: Friday, February 17, 2006 9:28 AM
> To: [hidden email]
> Subject: [saxon] intersection variable holds result correctly
> only once
>
> ...
> > Clearly, the overview line is still correct, but the first
> and third
> > line counting the number of occurrences of a specific message are
> > incorrect (reporting 50 occurences instead of 26 and 24,
> respectively).
> ...
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  
> DOWNLOAD SPLUNK!
> <a href="http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642">http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
> _______________________________________________
> saxon-help mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help
>




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
<a href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642">http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
saxon-help mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help