Based on feedback from Rick and Rony, I propose that we (I'll actually
do it) do this with the bugs
* Create a new category: WSH
Change the WSH bugs to:
Category: WSH
Resolution: Postponed
Status: Pending
That way the bugs are still easily retrievable, they are no longer in
the open state,
All,
As you may have noticed, I've recently been trying to clean up the
tracker bugs a little bit.
I'm planning on closing the WSH bugs as out of date.
No matter what, the old WSH code is not going to be used in the
future. It used undocumented, (unsafe ?) APIs that no longer exist,
and won't
As far as I can recall there is an open promise to turn to implementing
the WSH/ActiveX functionality for the new ooRexx interpreters,
sometimes after 4.0 goes GA.
The reasons given back then (why it did not get implemented for the
initial 4.0) were that no code from the 3.x line could be used
On Wed, Aug 11, 2010 at 9:00 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
As far as I can recall there is an open promise to turn to implementing
the WSH/ActiveX functionality for the new ooRexx interpreters,
sometimes after 4.0 goes GA.
There was.
But, nothing you bring up
On Wed, Aug 11, 2010 at 12:26 PM, Mark Miesfeld miesf...@gmail.com wrote:
On Wed, Aug 11, 2010 at 9:00 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
As far as I can recall there is an open promise to turn to implementing
the WSH/ActiveX functionality for the new ooRexx
On Wed, Aug 11, 2010 at 10:30 AM, Rick McGuire object.r...@gmail.com wrote:
On Wed, Aug 11, 2010 at 12:26 PM, Mark Miesfeld miesf...@gmail.com wrote:
There is absolutely no point in keeping bugs open when there is no
intention of fixing them. In this case there is no intention to fix
that
