I've got an app I've all but ported to 1.1.x that uses ORO, which, of course, is targeting more recent versions of Java. The most useful thread in the archives seems to be this one:
http://mail-archives.apache.org/mod_mbox/jakarta-oro-user/200209.mbox/%3c200 [EMAIL PROTECTED] Date: Sat, 21 Sep 2002 04:39:06 GMT >> If not, how difficult would it be to make a J2ME >> compatible version ? > > It's very easy to make the source code modifications if you limit > yourself to the .regex package (and maybe the .perl as well). The hard > part is to set up an acceptable build system and conditional compilation > mechanism to simultaneously support multiple versions for the various > incarnations of the Java platform. Which reminds me, I need to get back > to Didge about his proposed Ant task that uses Velocity macros for > conditional compilation. At any rate, the changes for J2ME may be a > little more than they used to be. It used to be that all you needed to > do was remove 'implements java.io.Serializable' and replace > Character.isWhitespace(char) calls with a custom implementation > (see http://www.savarese.org/talks/hjug-042000/img24.htm). > Now you would also have to change the Hashmaps to Hashtables, the ArrayLists > to Vectors, and there may be some issue with references to Collections > Framework interfaces. At any rate, it's not infeasible to support > J2ME and JDK 1.1.x with #ifdefs, but there has not been sufficient > demand to motivate the process of evaluating and deciding upon an > appropriate way to handle conditional compilation. We've talked about > it and I've ranted about Java's lack of real conditional compilation > since 1996. But you may be the first person with enough of an itch > to start scratching. In any case, J2ME support is another way to > distinguish ORO from J2SE 1.4's java.util.regex and I think it's > a good thing. So, as Jon is fond of saying, you just volunteered > for the job. > > daniel Any luck with the forced volunteering from several years ago? I'd offer my own limited 'skillz', but with my track record of finishing open source contributions I'd better not. That said, I do have some convenience files for porting to 1.1.x at this project: http://sourceforge.net/projects/joneone/ .. so admittedly I'll probably take a look if nobody else has and I can figure out the fewest files I need to get regexp working. Perhaps there's an older version that's 1.1.x happy? I have tried the other regexp package on jakarta, but it's proven a bit buggy with larger tasks in my experience. Fwiw, I'm only using a few objects for some simple regexps: import org.apache.oro.text.regex.MatchResult; import org.apache.oro.text.regex.Pattern; import org.apache.oro.text.regex.PatternCompiler; import org.apache.oro.text.regex.PatternMatcher; import org.apache.oro.text.regex.PatternMatcherInput; import org.apache.oro.text.regex.Perl5Compiler; import org.apache.oro.text.regex.Perl5Matcher; Can I volunteer anyone to jump start me an let me know what I'll need to port along with those (support files -- eg, just the regex namespace?)? Thanks for any help, Ruffin Bailey --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
