[io] Regexp filter - help wanted

[Stephen Colebourne <sc...@btopenworld.com>]

The regexp file filter has been excluded from [io] releases as [io] is 
JDK 1.2 compliant, see http://issues.apache.org/jira/browse/IO-74.

It would however be possible to use reflection to access the JDKs regexp 
facility. Is there anyone, perhaps who is looking to contribute to 
commons for the first time, who would be interested in seeing if this 
approach is viable, and what performance penalty it carries?

Obviously the reflection solution involves using Strings to find if the 
java.util.regex.Pattern exists, and then using reflection to call its 
methods.

Note that there is an alternative of using ORO, but I believe we should 
stick with the 'no dependencies' rule for [io] (even one that would be 
optional). And we should at least examine the releaction option.

Stephen

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

Re: [io] Regexp filter - help wanted

[Henri Yandell <fl...@gmail.com>]

On 7/27/06, Torsten Curdt <tc...@apache.org> wrote:
> > The regexp file filter has been excluded from [io] releases as [io] is
> > JDK 1.2 compliant, see http://issues.apache.org/jira/browse/IO-74.
> >
> > It would however be possible to use reflection to access the JDKs regexp
> > facility. Is there anyone, perhaps who is looking to contribute to
> > commons for the first time, who would be interested in seeing if this
> > approach is viable, and what performance penalty it carries?
> >
> > Obviously the reflection solution involves using Strings to find if the
> > java.util.regex.Pattern exists, and then using reflection to call its
> > methods.
>
> Actually this raises a different question IMO:
> How much real world is 1.2 compliance anymore?
>
> IMO we should raise the bar - for other components as well.

Agreed. Doing lots of work to keep on a 1.2 dependency isn't worth it.
I doubt that people who are on 1.2 JVMs (or even probably 1.3 JVMs)
are upgrading components or writing new code. Instead we should just
worry about 1.2 if we have to do a critical bugfix release of an old
version (very rare in Commons).

Moving from 1.4 to 1.5 will be a much bigger step due to the class
version change, so I can see that being a lot more complicated.

Hen

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

Re: [io] Regexp filter - help wanted

[Torsten Curdt <tc...@apache.org>]

> The regexp file filter has been excluded from [io] releases as [io] is
> JDK 1.2 compliant, see http://issues.apache.org/jira/browse/IO-74.
>
> It would however be possible to use reflection to access the JDKs regexp
> facility. Is there anyone, perhaps who is looking to contribute to
> commons for the first time, who would be interested in seeing if this
> approach is viable, and what performance penalty it carries?
>
> Obviously the reflection solution involves using Strings to find if the
> java.util.regex.Pattern exists, and then using reflection to call its
> methods.

Actually this raises a different question IMO:
How much real world is 1.2 compliance anymore?

IMO we should raise the bar - for other components as well.

cheers
--
Torsten

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