My summary of the discussion that I started:
1 Many thanks to everybody, who responds;
2 I didn't know about 'pluggable' ORO possibilty,
I'll take a look at this (puting something in commons
only to have 'commons' in package name is not a good idea);
3 I agree that totally 'bootstraping'
From: Tomasz Pik [EMAIL PROTECTED]
Original Message
Java 1.4 has a new regex package, and there are others
that could be
considered if a reliance on 1.4 is to be avoided.
Maybe something like 'Commons Logging' - one hat (with limited
Daniel Rall wrote:
Jeff Dever [EMAIL PROTECTED] writes:
Jakarta does have a top level regexp project:
http://jakarta.apache.org/regexp/
Jakarta Regexp is the more simple of the two Jakarta regex packages (I
believe that Tomcat uses this one). ORO is much more full featured,
offering
: Re: next possible commons project - [regexp]
Daniel Rall wrote:
Jeff Dever [EMAIL PROTECTED] writes:
Jakarta does have a top level regexp project:
http://jakarta.apache.org/regexp/
Jakarta Regexp is the more simple of the two Jakarta regex packages (I
believe that Tomcat uses
Jeff Dever [EMAIL PROTECTED] writes:
Jakarta does have a top level regexp project:
http://jakarta.apache.org/regexp/
Jakarta Regexp is the more simple of the two Jakarta regex packages (I
believe that Tomcat uses this one). ORO is much more full featured,
offering the full power of Perl 5
Stephen Colebourne wrote:
In the same way as [logging], by not being a regexp package itself.
Of course it may just not be appropriate...
To be honest, I don't like the autodiscovery mechanisms in Commons
logging. I would be hard pressed to support another something like
that for something
Stephen Colebourne writes:
In the same way as [logging], by not being a regexp package itself.
Of course it may just not be appropriate...
I just want to point out that jakarta-oro is more than just a regular
expression package and already contains the generic interfaces to wrap other
packages
I just want to point out that jakarta-oro is more than just a regular
expression package and already contains the generic interfaces to wrap
other
packages (as it is, oro already implements 3 different regular expression
grammars). It's a simple matter to add a factory to generate generic
On Thursday 26 September 2002 12:27 pm, Berin Loritsch wrote:
Stephen Colebourne wrote:
In the same way as [logging], by not being a regexp package itself.
Of course it may just not be appropriate...
To be honest, I don't like the autodiscovery mechanisms in Commons
logging. I would be
Steve Downey wrote:
The odds of having two projects that require regexp packages that can also
tolerate having the definition of regular expression changed underneath them
approaches zero.
I agree with this as far as most applications are concerned. I don't
know the original motivation for
On Thursday 26 September 2002 02:35 pm, Daniel F. Savarese wrote:
Steve Downey wrote:
The odds of having two projects that require regexp packages that can also
tolerate having the definition of regular expression changed underneath
them approaches zero.
I agree with this as far as most
Steve Downey [EMAIL PROTECTED] writes:
On Thursday 26 September 2002 12:27 pm, Berin Loritsch wrote:
Stephen Colebourne wrote:
In the same way as [logging], by not being a regexp package itself.
Of course it may just not be appropriate...
To be honest, I don't like the
12 matches
Mail list logo
