You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oro-dev@jakarta.apache.org by df...@apache.org on 2001/05/21 00:46:09 UTC
cvs commit: jakarta-oro TODO CHANGES
dfs 01/05/20 15:46:09
Modified: . TODO CHANGES
Log:
Clarified TODO and updated CHANGES (see diff).
Revision Changes Path
1.5 +7 -7 jakarta-oro/TODO
Index: TODO
===================================================================
RCS file: /home/cvs/jakarta-oro/TODO,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- TODO 2001/05/20 06:04:59 1.4
+++ TODO 2001/05/20 22:46:08 1.5
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.4 2001/05/20 06:04:59 dfs Exp $
+$Id: TODO,v 1.5 2001/05/20 22:46:08 dfs Exp $
o Optimize/improve Unicode character classes.
@@ -27,11 +27,11 @@
an interface's virtual function versus direct character array indexing.
If HotSpot dynamically inlines the functions and achieves comparable
performance, provided a clear warning is indicated that performance
- will be reduced on earlier JDK versions, create a generic interface
- for representing input. CharStringPointer should be replaced with
- a generic interface, PatternMatcherInput should be made to implement
- the interface, and stream matching can be reintroduced.
- Reintroduced stream matching should include a callback mechanism in the
+ could be reduced on earlier JDK versions, could create a generic interface
+ for representing input. Input array indexing could be replaced with
+ the generic interface, PatternMatcherInput could be made to implement
+ the interface, and stream matching could be reintroduced.
+ Reintroduced stream matching could include a callback mechanism in the
interface to report when a "contains" match has been found to allow
the input encapsulator to trim its buffer. Strong warnings must go
into the documentation referencing the ACM paper and noting that for
@@ -40,7 +40,7 @@
regular expressions will cause the whole stream to be read in anyway.
For situations where that is not the case we want to be able to trim
the buffer (there have been people who used OROMatcher to search
- gigabyte length files!). Additional methods should be added to
+ gigabyte length files!). Additional methods could be added to
regulate buffer growth behavior, whether to save all of it for reuse
in a future pass, etc.
1.10 +5 -1 jakarta-oro/CHANGES
Index: CHANGES
===================================================================
RCS file: /home/cvs/jakarta-oro/CHANGES,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- CHANGES 2001/05/20 10:53:52 1.9
+++ CHANGES 2001/05/20 22:46:08 1.10
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.9 2001/05/20 10:53:52 dfs Exp $
+$Id: CHANGES,v 1.10 2001/05/20 22:46:08 dfs Exp $
Version 2.x
@@ -9,6 +9,10 @@
o Fixed a problem in Perl5Debug.printProgram where it wouldn't handle
the printing of the unicode character class bytecode correctly.
+
+o Added links to Jakarta ORO home page in javadocs and converted
+ web site documentation to jakarta-site2 xml docs stored in xdocs
+ directory.
o Applied Mark Murphy's patch to add case modification support to
Perl5Substitution. The \u\U\l\L\E escapes from Perl5 double-quoted