There are two potential approaches to getting orxscript cleaned up that I see. The first approach would be to just "get it working". This is still a significant effort because the old code relied on a number of private APIs that could best be described as hacks. They didn't really make sense in the new interpreter structure and really weren't that well thought out to begin with. Those APIs ended up on the cutting room floor and getting things to work with the new API framework will require a bit of code restructuring.
The second approach would be to create a new set of APIs based on the Java JSR 233 specification for Java scripting. These new APIs would form a better basis for the orxscript support that would allow better interoperability between the Windows scripting engine and the ooRexx scripts. This approach would probably take longer, but have big long term benefits, such as enabling better levels of BSFRexx integration. Implementing this might take more than 3 months, but I doubt it would take too much more. I can deal with either approach. If we go with 1), something tells me we'd end up converting it to 2) eventually anyway. Regardless of the approach decided upon, I'm definitely in favor of a 4.0 release without orxscript. There are huge improvements in this release, including the 64-bit support that people have been clamoring for. Rick On Thu, Oct 2, 2008 at 12:11 PM, Mark Miesfeld <[EMAIL PROTECTED]> wrote: > As I'm sure anyone reading this knows, the next official release of > ooRexx is going to be 4.0.0. A major release with a big internal code > improvement, but also quite a bit of new stuff at the user level. > > And, I'm sure everyone is aware we haven't had an official release > since last November. We'd all like to get the release out the door. > There still is significant documentation and testing to be done, but I > think we can see the light at the end of the tunnel there. > > However, there is one large item that remains undone. The orxscript > extension is currently turned off in the build because it has not been > updated and is not currently working. Getting it ready to go, I > think, will take a significant amount of time. > > So, I'm going to float this idea / proposal to the list, see what others > think. > > I think it is quite possible that a lot of people / users would rather > see 4.0.0 released sooner with orxscript support turned off than wait, > what will surely be an added 3 months or so, for 4.0.0 with orxscript. > Then we could commit to getting a minor release with orxcript turned > back on as quickly as possible. Probably commit to not start any new > work and just focus on orxscript until that minor release was done. > > I anticipate that the minor release could be done about 3 months after > the major 4.0.0 release. Chances are good that we would also have a > few bug fixes in that minor release, making it a good general release. > Not just a Windows update. > > I'd like to know what people think about this. I'll float it by > RexxLA after / if there is a consensus here that it is acceptable. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
