I'm going to be a little hit and miss here and will probably respond in a couple of different posts.
On Sat, May 2, 2009 at 6:55 AM, Rick McGuire <object.r...@gmail.com> wrote: > 2) Compatibility. I'm not sure what to do here. I spent some time > reading the 3.2.0 WSH docs this morning, and I found a few things > quite appalling. The base scripting support just barely works because > of how variables are managed between the different script fragments. > We have a couple of bugs open against those characteristics already, > and just fixing those bugs will result in come differences in > behavior. I'd be in favor here of saying to the user community: Look, the old WSH was simply not done right. In order to do it right we basically need to scrap the old WSH and build a new WSH. This will result in incompatibility with the old WSH, but a far more useful and functional new WSH. If you simply can not use a WSH that is incompatible, then we suggest you stay with ooRexx 3.2.0. I think we'll be able to judge how plausible it is that the user community will accept the above, by what happens when ooRexx 4.0.0 is actually released. We know the people who follow the devel list, RexxLA, and comp.lang.rexx are aware 4.0.0 will ship without WSH. So, I expect they would be comfortable with the above argument. The response was 100% to release 4.0.0 without WSH. What we don't know yet is how many people are using WSH that don't follow those lists. We'll see how many people complain after we do the actual release. > I have no sense on how many people are actually using the WSH > capabilities. Given the state of the code, I would have expected > there to be a larger number of bug reports or RFEs against this > component if people were using it for real things. There were a couple of relatively simple bugs that I fixed, that at the time I thought would have bit a lot of people using WSH. Yet only one person opened a bug. That gave me the sense that not a lot of people were using it. That's why I think the offering of a useful, functional WSH would be appealing. -- Mark Miesfeld ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
