Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!att!cbnewsc!fjo From: fjo@cbnewsc.ATT.COM (frank.j.owen) Newsgroups: comp.sys.mac.programmer Subject: Re: Problem with LSC 4.0 debugger. Message-ID: <3473@cbnewsc.ATT.COM> Date: 26 Sep 89 15:07:45 GMT References: <1563@atanasoff.cs.iastate.edu> Distribution: na Organization: AT&T Bell Laboratories Lines: 22 From article <1563@atanasoff.cs.iastate.edu>, by jwright@atanasoff.cs.iastate.edu (Jim Wright): > How should recursive functions be handled? Are they a special case at all? > Do you really want to allow local variables be changed in calling functions? Recursive functions do NOT need to be handled specially. The PRESENT debugger will show each seperate instance of the function that appears in the current calling chain. They are all listed with the same name if we are looking at recursive invocations. You are probably right that it may not be a prudent thing to change local variables in a called function, but this is a debugger we are talking about. It should let you do alot of things that may not (or perhaps may) be prudent. I have personally found it very useful to at least be able to LOOK at the local variables of both the calling and called functions. They can tell you alot about the state of the machine when a call was made. -- Frank Owen 312-982-2182 AT&T Bell Laboratories 5555 Touhy Ave., Skokie, IL 60077 PATH: ...!att!ihc!fjo