Re: Detecting endless recursion?

Uli Kusterer <witness@t-online.de>
1 Feb 2004 12:33:26 -0500

          From comp.compilers
Related articles
[10 earlier articles]
Re: Detecting endless recursion? vbdis@aol.com (2004-01-16)
Re: Detecting endless recursion? joachim.durchholz@web.de (Joachim Durchholz) (2004-01-18)
Re: Detecting endless recursion? nmm1@cus.cam.ac.uk (2004-01-22)
Re: Detecting endless recursion? lex@cc.gatech.edu (Lex Spoon) (2004-01-22)
Re: Detecting endless recursion? torbenm@diku.dk (2004-01-31)
Re: Detecting endless recursion? witness@t-online.de (Uli Kusterer) (2004-01-31)
Re: Detecting endless recursion? witness@t-online.de (Uli Kusterer) (2004-02-01)
Re: Detecting endless recursion? witness@t-online.de (Uli Kusterer) (2004-02-01)
Re: Detecting endless recursion? joachim.durchholz@web.de (Joachim Durchholz) (2004-02-01)
Re: Detecting endless recursion? joachim.durchholz@web.de (Joachim Durchholz) (2004-02-01)
Re: Detecting endless recursion? nmm1@cus.cam.ac.uk (2004-02-01)
Re: Detecting endless recursion? derkgwen@HotPOP.com (Derk Gwen) (2004-02-01)
Re: Detecting endless recursion? lex@cc.gatech.edu (Lex Spoon) (2004-02-01)
[10 later articles]
| List of all articles for this month |
From: Uli Kusterer <witness@t-online.de>
Newsgroups: comp.compilers
Date: 1 Feb 2004 12:33:26 -0500
Organization: T-Online
References: 04-01-050 04-01-086 04-01-119
Keywords: debug, courses
Posted-Date: 01 Feb 2004 12:33:26 EST

  Joachim Durchholz <joachim.durchholz@web.de> wrote:


> Since the tool is going to be educational, I assume that the users


Actually, it won't be educational in that sense. It's a decent
programming language, but the main target audience is people who aren't
familiar with programming. They should be able to just try out things
without having the bugger crash on them.


> will be able to halt the execution and inspect the stack state. In
> this situation, tail call optimization is something that should not be
> done: the users will complain that the tool has removed information
> (all those intermediate stack frames that got eliminated due to tail
> call optimization).


  Yeah, debuggability is an important argument against such optimizations
here, though there are ways around that.


Cheers,
-- Uli
http://www.zathras.de <-- back up again!

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.