On Thu, Feb 4, 2016 at 8:59 AM, Jon Wolfers <sahana...@gmail.com> wrote:
>
> Now, given that it isn't possible to have all rexx interpreters working
> exactly the same, because we see such a spread of behaviour, and that the
> current behaviour in ooRexx for Windows and Linux has been in place for a
> long time, I would say that changing this behaviour to match some behaviour
> that might have existed on some interpreter on some platform in the past
> would break more currently active code than recognising that this change
> may have occurred in the past and that the helpfile is ambiguous and
> correcting the helpfile suitably.
>
I fully agree. We should be more concerned about not breaking ooRexx
instead of making it compatible to some other version of Rexx. I'd vote for
adjusting the documentation and leave it as that. We could even add a note
saying that ooRexx's directory bif might be different from old versions of
Rexx.
Moritz
--
Moritz Hoffmann;
http://antiguru.de/
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
