You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oro-user@jakarta.apache.org by "Daniel F. Savarese" <df...@savarese.org> on 2001/05/09 21:26:29 UTC

jakarta-oro 2.0.2 released

Since there have been no bug reports for 2.0.2dev2 and people seem
to have been sticking with 2.0.1 which has some bugs, I've tagged
the current source as release-2-0-2 and released a 2.0.2 build.

This week I'll do what I promised and post a proposed development
plan.  I'm going to suggest a staged plan where we gradually add
and test certain features.  The plan will be based around getting
all of the Perl stuff up to 5.6 compatibility.  That version will
be sufficiently different that it should be version 3.0.  The
steps in between will have 2.1, 2.2, etc. targets.

Even though the emphasis is on the Perl regex stuff, since that's the
most popular functionality, the jakarta-oro project is supposed to
be a general text processing library, so I'll make suggestions about
additional features, such as tokenizers, that could be added on the
road to 3.0 or delayed until after then.  I'll also propose a project
definition statement to precisely scope the project.  Anyway, it'll
be up for discussion in a few days.

BTW, Mark, where's that Perl5Substitution patch you were going to
post?  I know, who am I to talk, I haven't followed through on
my stuff yet.

daniel



Re: jakarta-oro 2.0.2 released

Posted by "Mark F. Murphy" <ma...@tyrell.com>.
At 3:26 PM -0400 5/9/01, Daniel F. Savarese wrote:
>BTW, Mark, where's that Perl5Substitution patch you were going to
>post?

Sorry.

Been busy.

I do have a question about coding styles.

I read over the Java coding style and maybe have a couple differences 
between mine and it.

I tend to comment in order to separate areas of code.

Is that a problem?

If I submit the diff posting, do you integrate the diff in or do you 
further massage it into the tree?

Also, what about testing?

I've done some unit testing (and the code changes are in our own 
production system now)... but how does this thing get extensively 
tested to make sure I didn't break anything?

I did change a couple behaviors to be more perl like with respect to 
the substitution string.

Like if a replacement group int is not found, it is simply no text 
where as the current behavior shows a '$' and the int value.

In perl, such a substitution would yield no text.

I also added escpaping (had to for \[ulULE]) for both '$' and '\'.

So just want to make sure I'm doing the process correct.

Thanks for any feedback.

I'll make any adjustments you say I might need to make or I can just 
post the diff.

mark

-- 
---------------------------------------------------------------------------
  Mark F. Murphy, Director Software Development   <ma...@tyrell.com>
  Tyrell Software Corp                            <http://www.tyrell.com>
  PowerPerl(tm), Add Power To Your Webpage!       <http://www.powerperl.com>
---------------------------------------------------------------------------
  Families Against Internet Censorship:        http://www.netfamilies.org/

Dev Plan

Posted by "Mark F. Murphy" <ma...@tyrell.com>.
At 3:26 PM -0400 5/9/01, Daniel F. Savarese wrote:
>...so I'll make suggestions about
>additional features, such as tokenizers, that could be added on the
>road to 3.0 or delayed until after then.  I'll also propose a project
>definition statement to precisely scope the project.  Anyway, it'll
>be up for discussion in a few days.

What about performance enhancements?

Any need for that?

mark

-- 
---------------------------------------------------------------------------
  Mark F. Murphy, Director Software Development   <ma...@tyrell.com>
  Tyrell Software Corp                            <http://www.tyrell.com>
  PowerPerl(tm), Add Power To Your Webpage!       <http://www.powerperl.com>
---------------------------------------------------------------------------
  Families Against Internet Censorship:        http://www.netfamilies.org/

Re: jakarta-oro 2.0.2 released

Posted by Jon Stevens <jo...@latchkey.com>.
on 5/10/01 2:44 AM, "Takashi Okamoto" <to...@rd.nttdata.co.jp> wrote:

> http://jakarta.apache.org/site/binindex.html
> This page is linking ORO 2.0.1. It's obsolete.

Fixed. 

In the future, you could submit a diff to fix this...

Read:
<http://jakarta.apache.org/site/jakarta-site2.html>

-jon

-- 
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>


Re: jakarta-oro 2.0.2 released

Posted by Takashi Okamoto <to...@rd.nttdata.co.jp>.
Hi!!

From: "Daniel F. Savarese" <df...@savarese.org>
> Since there have been no bug reports for 2.0.2dev2 and people seem
> to have been sticking with 2.0.1 which has some bugs, I've tagged
> the current source as release-2-0-2 and released a 2.0.2 build.

Congratulations!

Wel,l I have a few comments this release.

in CHANGES
--
o Applied a modified version of Takashi Okamoto's unicode/posix patch.
  It adds unicode support to character classes and adds partial support
  for posix classes (it supports things like [:digit:] and [:print:], but
  not [:^digit:] and [:^print:]).  It will be improved/optimized later, but
  gives people the functionality they need today.
--

[:^digit:] and [:^print:]) are worked fine. It was fixed already.

http://jakarta.apache.org/site/binindex.html
This page is linking ORO 2.0.1. It's obsolete.

Thanks.
--------------------------------------------
Takashi Okamoto



Re: Yow... No More Java 1.1 Support?

Posted by "Mark F. Murphy" <ma...@tyrell.com>.
At 1:09 PM -0700 5/10/01, Jon Stevens wrote:
>  > For example, some software written in Java might have dependencies on
>>  a particular JDK and not be certified to work in newer JDKs.
>
>Right...and my point is that you have had *years* to test things.

I'm *not* talking about *my* code but code from a vendor that is not 
certified nor runs under JDK greater than 1.1.8... for example.

>  > I'm questioning what is gained by making Jakarta-Ora *not* compatible
>>  with JDK 1.1?
>
>We can take advantage of JDK 1.2 features.

Understood.

If there's a compelling feature that 1.2 offers that cannot be done 
otherwise, I understand.

If there's some huge benefit to be gained because of the abstraction, 
I understand.

Simply changing for the sake of changing, I have a more difficult time with.

For example, changing from Vector to ArrayList in Perl5Substitution 
seemed to be changed just because (no offense to the person who made 
the change).

>  > Most C based regex packages are done with just C.
>
>C != Java

I know that.

My point is (and perhaps I wasn't clear) that I don't see a huge 
benefit in using Java classes which may not gain much (or nothing at 
all) that couldn't be done in the base Java lang... much like the 
original regex packages are done in.

A good example would be the overuse of String in java code.

A very typical mistake by junior java developers which can affect 
memory size, performance, etc.

Just because a class exists in the JDK doesn't mean one should use it.

Careful consideration must be given to the scope of the work being 
done... and what the goal is.

For a Java regex package, my opinion would be that performance is 
important... and compatibility with other regex expressions is high 
on the list (as in the Perl module).

Using the latest and greatest Java classes in JDK X might not be a 
requirement nor needed when analyzing the design.

>  > Haven't you ever run into a deployment situation where you were stuck
>>  with an older version of a dev system or dependent libraries?
>
>Not with Java. All my JDK 1.1 code instantly worked on JDK 1.2 and 1.3
>without any problems other than maybe a re-compile. Java is great at forward
>compatibility.

All my code works like that as well.

But I'm not talking about *my* code.

I'm talking about when one is dependent on other vendor classes or 
environments where going to a newer JDK isn't possible.... yet the 
need to still develop or add code to that environment is a 
requirement.

Jakarta-Oro is a great tool... I've used it in several projects.

>Let me guess...you also still use Windows 3.1.

No, I don't.

But let me guess... you must be a bit bent out of shape.... or at 
least that's the feeling I'm getting.

Otherwise, I'm at a loss for the negativism in your replies.

>Nearly *every* project within Jakarta now has a dependency on JDK 1.2. Time
>for you to upgrade sir.

I'll repeat... it's not a matter of *my* code needing upgrading.

It's a matter of in a deployment situation being dependent on other 
vendors where the environment cannot change past JDK 1.1.x.

Is jakarta-oro only meant to work/integrate with apache products and 
nothing else?

I hope not.

Perhaps I misunderstand the goals of the jakarta-oro project?

mark

-- 
---------------------------------------------------------------------------
  Mark F. Murphy, Director Software Development   <ma...@tyrell.com>
  Tyrell Software Corp                            <http://www.tyrell.com>
  PowerPerl(tm), Add Power To Your Webpage!       <http://www.powerperl.com>
---------------------------------------------------------------------------
  Families Against Internet Censorship:        http://www.netfamilies.org/

Re: Yow... No More Java 1.1 Support?

Posted by Jon Stevens <jo...@latchkey.com>.
on 5/10/01 12:30 PM, "Mark F. Murphy" <ma...@tyrell.com> wrote:

> At 11:45 AM -0700 5/10/01, Jon Stevens wrote:
>> Oh come on. Upgrade your JDK. You have had warning that the support would go
>> away.
>> 
>> JDK 1.2 has been out for *years* now and is supported on all the major
>> platforms except MacOS9.
> 
> Not very helpful.
> 
> There are *deployment* situations where it is not possible to upgrade the JDK.
> 
> For example, some software written in Java might have dependencies on
> a particular JDK and not be certified to work in newer JDKs.

Right...and my point is that you have had *years* to test things.

> I realize that a *warning* was given...

Exactly.

> I'm questioning what is gained by making Jakarta-Ora *not* compatible
> with JDK 1.1?

We can take advantage of JDK 1.2 features.

> Switching from Vector to ArrayList hardly seems like a *reason*.
> 
> I could understand the reliance on JDK 1.2 if there was a compelling
> reason... like performance... some class that was in 1.2 that was
> absolutely necessary.
> 
> But we are talking a regex package here.
> 
> Most C based regex packages are done with just C.

C != Java

> Haven't you ever run into a deployment situation where you were stuck
> with an older version of a dev system or dependent libraries?

Not with Java. All my JDK 1.1 code instantly worked on JDK 1.2 and 1.3
without any problems other than maybe a re-compile. Java is great at forward
compatibility.

Let me guess...you also still use Windows 3.1.

Nearly *every* project within Jakarta now has a dependency on JDK 1.2. Time
for you to upgrade sir.

-jon

-- 
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>


Re: Yow... No More Java 1.1 Support?

Posted by "Mark F. Murphy" <ma...@tyrell.com>.
At 11:45 AM -0700 5/10/01, Jon Stevens wrote:
>Oh come on. Upgrade your JDK. You have had warning that the support would go
>away.
>
>JDK 1.2 has been out for *years* now and is supported on all the major
>platforms except MacOS9.

Not very helpful.

There are *deployment* situations where it is not possible to upgrade the JDK.

For example, some software written in Java might have dependencies on 
a particular JDK and not be certified to work in newer JDKs.

I realize that a *warning* was given...

But...

I'm questioning what is gained by making Jakarta-Ora *not* compatible 
with JDK 1.1?

Switching from Vector to ArrayList hardly seems like a *reason*.

I could understand the reliance on JDK 1.2 if there was a compelling 
reason... like performance... some class that was in 1.2 that was 
absolutely necessary.

But we are talking a regex package here.

Most C based regex packages are done with just C.

I'd find it hard to believe that Oro must rely on 1.2.

Haven't you ever run into a deployment situation where you were stuck 
with an older version of a dev system or dependent libraries?

It happens.

It can happen a lot.

mark

-- 
---------------------------------------------------------------------------
  Mark F. Murphy, Director Software Development   <ma...@tyrell.com>
  Tyrell Software Corp                            <http://www.tyrell.com>
  PowerPerl(tm), Add Power To Your Webpage!       <http://www.powerperl.com>
---------------------------------------------------------------------------
  Families Against Internet Censorship:        http://www.netfamilies.org/

Re: Yow... No More Java 1.1 Support?

Posted by Jon Stevens <jo...@latchkey.com>.
on 5/10/01 10:44 AM, "Mark F. Murphy" <ma...@tyrell.com> wrote:

> I've been using Jakarta-Oro 2.0 for some time now with JDK 1.1.x with
> no problems and there appeared to be no dependencies on JDK 1.2 even
> though the Changes for v2.0 says "Guaranteed compatibility with JDK
> 1.1 is discontinued".
> 
> It seems the first version of Jakarta-Oro to break JDK 1.1
> compatibility is 2.2.... exchanging out Vector with ArrayList.
> 
> Seems like such a small thing to change for breaking JDK 1.1 support.
> 
> Is there a compelling reason why Jakarta-Oro cannot accomplish the
> task of Regex and not be JDK 1.1 compatible?
> 
> mark

Oh come on. Upgrade your JDK. You have had warning that the support would go
away.

JDK 1.2 has been out for *years* now and is supported on all the major
platforms except MacOS9.

-jon


Yow... No More Java 1.1 Support?

Posted by "Mark F. Murphy" <ma...@tyrell.com>.
I've been using Jakarta-Oro 2.0 for some time now with JDK 1.1.x with 
no problems and there appeared to be no dependencies on JDK 1.2 even 
though the Changes for v2.0 says "Guaranteed compatibility with JDK 
1.1 is discontinued".

It seems the first version of Jakarta-Oro to break JDK 1.1 
compatibility is 2.2.... exchanging out Vector with ArrayList.

Seems like such a small thing to change for breaking JDK 1.1 support.

Is there a compelling reason why Jakarta-Oro cannot accomplish the 
task of Regex and not be JDK 1.1 compatible?

mark

-- 
---------------------------------------------------------------------------
  Mark F. Murphy, Director Software Development   <ma...@tyrell.com>
  Tyrell Software Corp                            <http://www.tyrell.com>
  PowerPerl(tm), Add Power To Your Webpage!       <http://www.powerperl.com>
---------------------------------------------------------------------------
  Families Against Internet Censorship:        http://www.netfamilies.org/

Re: jakarta-oro 2.0.2 released

Posted by Takashi Okamoto <to...@rd.nttdata.co.jp>.
Hi!!

From: "Daniel F. Savarese" <df...@savarese.org>
> Since there have been no bug reports for 2.0.2dev2 and people seem
> to have been sticking with 2.0.1 which has some bugs, I've tagged
> the current source as release-2-0-2 and released a 2.0.2 build.

Congratulations!

Wel,l I have a few comments this release.

in CHANGES
--
o Applied a modified version of Takashi Okamoto's unicode/posix patch.
  It adds unicode support to character classes and adds partial support
  for posix classes (it supports things like [:digit:] and [:print:], but
  not [:^digit:] and [:^print:]).  It will be improved/optimized later, but
  gives people the functionality they need today.
--

[:^digit:] and [:^print:]) are worked fine. It was fixed already.

http://jakarta.apache.org/site/binindex.html
This page is linking ORO 2.0.1. It's obsolete.

Thanks.
--------------------------------------------
Takashi Okamoto