About the OPT. I'll try to rewite my sentence: If someone decides to adapt the OPT interface to show Racket programs, I think that it will be necessary to add the support for tail calls. IIRC tail calls are not supported in Python, so I guess that the OPT don't show them properly, I guess it keeps all the call stack and when the inner function finish the return values travel to the top.
In Racket, the tail calls are more popular, so I think the tail calls should be explicitly handled in a "OPT for racket". This may be confusing for beginners, so perhaps it can be a configurable option. The main problem is that iterations are usually implemented as tail calls, so the complete call stack can be very big, so it's confusing to show them too. (Is it possible to show a few of the first and last functions calls and hide the 100-ish repeated middle calls?) Gustavo On Tue, Jul 14, 2015 at 10:48 AM, John Clements <[email protected]> wrote: > >> On Jul 11, 2015, at 9:46 PM, Gustavo Massaccesi <[email protected]> wrote: >> >> For a Racket version, it would be very helpful to have a special case >> for tail calls. > > Can you tell me what you mean by this? I’m not sure whether you’re talking > about the stepper or OPT. > > Thanks! > > John Clements > -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAPaha9NYHSxeqZSE4-93VvvaePWMRShVsvo-_TbGvQieHBMj3Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
