Re: debug: points where left on the stack

[Joerg Sommer <joerg@xxxxxxxxxxxx>]

"John E. Davis" <davis@xxxxxxxxxxxxx> wrote:
> Joerg Sommer <joerg@xxxxxxxxxxxx> wrote:
>>I'm interested in functions they leave values on the stack after quit
>>without using the return statement. I'm not interested in such constructs:
>>
>>do_check();
>>do_something();
>>if ( () )
>
> You should try to minimize the use of such constructs.

Why? Is a cool feature of slang.

>>Do you have a tool for this?
>
> All I can suggest is that you selectively use calls to
> enable_stack_check/disable_stack_check.  Also you see the same line
> appearing in the stack check output over and over again, and you
> believe that it is ok, then you should rewrite it, e.g,.
>
>    do_check ();
>    variable status = do_something ();
>    if (status) ...

Oh sorry, there is a mistake. I use:

   variable status = do_check ();
   do_something ();
   if (status) ...

Jörg.
-- 
Es gibt nichts schöneres als dem Schweigen eines Dummkopfes zuzuhören.
   	       		      	  	        (Helmut Quatlinger)

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.