>>>Just want to point out that needing to know all this is a reason to use ASTACKINFO(). You get an array with all the information you need, and the return value of the function is the number of levels.
>>>
>>>Tamar
>>
>>Hi Tamar, they where about speed issues of ASTACKINFO() vs PROGRAM(), since Dimtry likes to do this in an ACCESS_ method.
>
>I haven't tested speed of ASTACKINFO(), but I've used it pretty extensively in some various logging code without noticing slowdowns. When i use it, I tend to not only call it, but then loop through and build a string of the results.
>
>Tamar
Sounds familiar. Looping through PROGRAM() just for listing the stack sounds not wise since we have ASTACKINFO. But here it's just about who calls a method. I guess it might not be of much influence - if, the use of ACCESS_ might be the bigger problem.
I doubt the idea of figuring out who calls ACCESS_ method at all. I would check for action/write by a different property, but then, it's not my solution.
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord
Weeks of programming can save you hours of planning.
OffThere is no place like [::1]