Walter: Apologies! I'd never seen the Call Trace trick before. Signal is probably as good as anything else, unless Signal On whatever would catch it and prevent the desired action.
Maybe: call crash_burn_and_die just for the fun of it. Les On 9/7/2015 2:35 PM, Les Koehler wrote: > > > On 9/7/2015 12:58 PM, Walter Pachl wrote: >> I would vote for 2 (cheapest and honest solution) >> Add a sentence to each: >> Address hostemu 'TS' is equivalent to Call trace '?R' >> Address hostemu 'TE' is equivalent to Call trace 'O' >> Address hostemu 'HI' is equivalent to Signal halt > > Remove 'Call', it's not needed. > Change the last one to: exit > thus avoiding the 'Unknown label: halt > error msg. >> >> That's what I see with this little Test program >> >> Trace R >> Do i=1 To 100000 >> j=i**i >> If i<5 Then >> Say 'i='i 'j='j >> If i=2 Then >> address hostemu 'TS' >> If i=3 Then >> address hostemu 'TE' >> End >> Say i >> address hostemu 'HI' >> Say i >> ::requires hostemu LIBRARY >> >> Note that these subcommands can also be entered in lowercase or mixed case >> :-) >> >> Option 1: still cheaper but not quite as clear >> Option 3: As cheap as 2 but not quite as honest >> Option 4: Some effort and honest >> Option 5: I couldn't possibly estimate the (huge) effort and I doubt that >> the hostemu Library should/would play a role there >> >> Walter >> >> >> -----Ursprüngliche Nachricht----- >> Von: CVBruce [mailto:cvbr...@gmail.com] >> Gesendet: Montag, 07. September 2015 17:55 >> An: Open Object Rexx Users <oorexx-users@lists.sourceforge.net> >> Betreff: Re: [Oorexx-users] How to use HI, TS and TE in *nix (bash) >> >> 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 > ------------------------------------------------------------------------------ _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users