status of the patches

[Oleg Sukhodolsky <so...@ppson.spb.ru>]

Hi,

about two months ago I've submitted suggested fixes for two bugs.
I did it by attaching suggested fixes to bug-reports (one of two ways
suggested by apache) and so I'm not sure if they were noticed.
Here is a list of the bugs:

| 3303|New|Min|2001-08-28|Unicode 3.0 character \\uFFFD                     |
| 3773|New|Nor|2001-09-21|Problem with parsing greedy match modifiers       |

The main question is whether you (regexp developers) aware about these
patches?

Also I've evaluated three bugs and I would like to know what do you
think about my evaluations, because if I'm right these bugs should be
closed

[Bug 2121]   -     '.' or '-' in bracket expression gives unexpected results
[Bug 4137]   -     regexp match gets different results on different platforms
[Bug 18515]  -     Line anchor does not work when match starts at index > 0

With best regards, Oleg.

---------------------------------------------------------------------
To unsubscribe, e-mail: regexp-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: regexp-dev-help@jakarta.apache.org

Re: status of the patches

[Oleg Sukhodolsky <so...@ppson.spb.ru>]

Hi Vadim,

>>[Bug 4137]   -     regexp match gets different results on different platforms

> Actually, I'd expect that the program (probably on server) will 
> correctly work when some input is submitted from any clients with any 
> line endings. So, I'd think that either regexp should match any of \r\n, 
> \r, \n combination as a new line. Or, this behavior should be 
> configurable (DOS / UNIX / MAC / ANY)

I've attached suggested fix for this bug to bug-report.
I have not added any new configuration options because I'm not sure if
they are required (and it will be easy to add them later when users
request them).

With best regards, Oleg.

---------------------------------------------------------------------
To unsubscribe, e-mail: regexp-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: regexp-dev-help@jakarta.apache.org

Re: status of the patches

[Vadim Gritsenko <va...@verizon.net>]

Oleg Sukhodolsky wrote:

>Hi,
>
>about two months ago I've submitted suggested fixes for two bugs.
>I did it by attaching suggested fixes to bug-reports (one of two ways
>suggested by apache) and so I'm not sure if they were noticed.
>  
>

I think I missed those emails...


>Here is a list of the bugs:
>
>| 3303|New|Min|2001-08-28|Unicode 3.0 character \\uFFFD                     |
>| 3773|New|Nor|2001-09-21|Problem with parsing greedy match modifiers       |
>  
>

Patches look Ok; I might get to actually applying them some time...


>The main question is whether you (regexp developers) aware about these
>patches?
>
>Also I've evaluated three bugs and I would like to know what do you
>think about my evaluations, because if I'm right these bugs should be
>closed
>
>[Bug 2121]   -     '.' or '-' in bracket expression gives unexpected results
>  
>

To close this bug I think new flag should be introduced, 
MATCH_POSIXINTERVAL or something. It should not be really hard to 
implement posix behavior. Also, javadoc should be patched accordingly.


>[Bug 4137]   -     regexp match gets different results on different platforms
>  
>

Actually, I'd expect that the program (probably on server) will 
correctly work when some input is submitted from any clients with any 
line endings. So, I'd think that either regexp should match any of \r\n, 
\r, \n combination as a new line. Or, this behavior should be 
configurable (DOS / UNIX / MAC / ANY)


>[Bug 18515]  -     Line anchor does not work when match starts at index > 0
>  
>

Closing this one right away.

Thanks,
Vadim



---------------------------------------------------------------------
To unsubscribe, e-mail: regexp-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: regexp-dev-help@jakarta.apache.org