I vote for 3 and 5. Path 1 is the default if we cannot come to a consensus, or the issue just fades away due to lack of an easy solution.
Path 2 makes matters worse by drawing attention to the (useless) feature. Path 3 essentially deprecates a feature that duplicates existing functionality by removing all references (that we can find) to it. Path 4 should be left until we are certain that the code has no value. We don't have that for certain at this point. Path 5 allows us to investigate the problem. We don't know if it's hard or not until someone looks into it. If we can create an implementation of that feature in a manner that is consistent with the very useful functionality it provides on the mainframe implementation, we should do so. Needless to say, such an RFE won't have a very high priority unless someone just happens to be intrigued by the problem. -Chip- On 9/7/2015 11:54 AM, CVBruce wrote: > Let me summarize the discussion: > > 1. The hostemu environment commands “TS” “TE” and “HI” work as documented in > the ooRexx Rexx Extensions manual. > 2. The commands mentioned above although named like the CMS commands, don’t > work like the CMS commands. > 3. The commands mentioned above offer little if any additional functionality > to ooRexx. > > It would be interesting to hear from the author to understand his/her reason > for implementing the commands. > > Possible paths forward: > 1. Do nothing. > 2. Add documentation to clarify the use and restrictions of the current > commands. > 3. Remove documentation referring to the commands, i.e. make them > undocumented. > 4. Remove the commands from the software and documentation. > 5. Enter an RFE to change how the commands work to be compatible with the > workings of the CMS commands. > > Bruce >> On Sep 6, 2015, at 11:39 PM, Walter Pachl <christel.u.w.pa...@chello.at> >> wrote: >> >> Currently I see this: >> >> C:\Users\Walter>rexx loop >> 90000001 >> >> C:\Users\Walter>hi >> Der Befehl "hi" ist entweder falsch geschrieben oder >> konnte nicht gefunden werden. >> >> C:\Users\Walter>rexx loop >> 90000001 >> >> C:\Users\Walter>ts >> Der Befehl "ts" ist entweder falsch geschrieben oder >> konnte nicht gefunden werden. >> >> So my "immediate" commands are kept till my rexx ends. >> >> Not so on CMS >> >> Walter >> PS Der Befehl "xx" ist entweder falsch geschrieben oder konnte nicht >> gefunden werden. >> The 'xx' command was spelt incorrectly or could not be found >> -----Ursprüngliche Nachricht----- >> Von: J. Leslie Turriff [mailto:jlturr...@mail.com] >> Gesendet: Sonntag, 06. September 2015 21:07 >> An: Open Object Rexx Users <oorexx-users@lists.sourceforge.net> >> Betreff: Re: [Oorexx-users] How to use HI, TS and TE in *nix (bash) >> >> On Saturday 05 September 2015 21:10:57 CVBruce wrote: >>> I feel that I overstated the case, in that I do believe they are a >>> part of Rexx, in that they are supported in a particular Rexx >>> implementation. >>> There are always going to be locally implemented features that are >>> not universally available in every implementation of the language. >>> >>> Bruce >> >> Agreed; but if provided as an emulation of another platform's >> capabilities, they should actually provide that capability. >> >> -- >> A Caution to Everybody >> >> Consider the Auk; >> Becoming extinct because he forgot how to fly, and could only walk. >> Consider man, who may well become extinct >> Because he forgot how to walk and learned how to fly before he thinked. >> >> -- Ogden Nash >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Oorexx-users mailing list >> Oorexx-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-users >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Oorexx-users mailing list >> Oorexx-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-users > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Oorexx-users mailing list > Oorexx-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-users > ------------------------------------------------------------------------------ _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
