On 19.02.2012 18:56, Rick McGuire wrote: > On Sun, Feb 19, 2012 at 12:53 PM, Rony G. Flatscher > <[email protected]> wrote: >> On 19.02.2012 18:31, Rick McGuire wrote: >>> On Sun, Feb 19, 2012 at 12:23 PM, Rony G. Flatscher >>> <[email protected]> wrote: >>>> After researching a while (starting out with .context) I ended up in the >>>> native API to look for the >>>> name of the current routine for which the exit runs, i.e. GetRoutineName(). >>>> >>>> Unfortunately, this API is only available in the "function" context and >>>> not in the "exit" context. >>>> >>>> Would it be in general possible/feasible for the exit context to get at >>>> the routine's name (and >>>> maybe even at the name of the label to which control may have gotten >>>> transferred to with a call or a >>>> signal)? >>> No it would not. Routine name in this context is the name of the >>> routine that the function is being invoked as. This is not the name >>> of the routine that happens to be running. This makes no sense to add >>> to the exit APIs. >> Thank you for this clarification! >> (So RXINI and RXTER exit cannot be really used for measuring time as it is >> not possible to figure >> out the program they run for.) > I can't think of any situations where they would be different, except > possibly some error exception handling situations, and even that is > just speculation. Thanks again a lot, will have to try to research even more then...
---rony ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
