> To improve efficiency, this patch moves the limit check to within the Lexer
> and reports any overlimit situation as soon as it happens.
>
> Note the change in XPathParser: diff (and also webrevs) showed the whole
> error-report block was changed, the actual change was only placing the block
On Thu, 7 Jul 2022 17:32:45 GMT, Joe Wang wrote:
>> To improve efficiency, this patch moves the limit check to within the Lexer
>> and reports any overlimit situation as soon as it happens.
>>
>> Note the change in XPathParser: diff (and also webrevs) showed the whole
>> error-report block
On Fri, 1 Jul 2022 17:04:10 GMT, Joe Wang wrote:
> To improve efficiency, this patch moves the limit check to within the Lexer
> and reports any overlimit situation as soon as it happens.
>
> Note the change in XPathParser: diff (and also webrevs) showed the whole
> error-report block was
On Fri, 1 Jul 2022 17:04:10 GMT, Joe Wang wrote:
> To improve efficiency, this patch moves the limit check to within the Lexer
> and reports any overlimit situation as soon as it happens.
>
> Note the change in XPathParser: diff (and also webrevs) showed the whole
> error-report block was
On Fri, 1 Jul 2022 17:04:10 GMT, Joe Wang wrote:
> To improve efficiency, this patch moves the limit check to within the Lexer
> and reports any overlimit situation as soon as it happens.
>
> Note the change in XPathParser: diff (and also webrevs) showed the whole
> error-report block was
To improve efficiency, this patch moves the limit check to within the Lexer and
reports any overlimit situation as soon as it happens.
Test: java.xml tests passed.
-
Commit messages:
- 8289486: Improve XSLT XPath operators count effiency
Changes:
