Xref: utzoo comp.compilers:1378 comp.lang.scheme:1751 comp.lang.lisp:3813 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!olivea!mintaka!spdcc!esegue!compilers-sender From: ham@Neon.Stanford.EDU (Peter R. Ham) Newsgroups: comp.compilers,comp.lang.scheme,comp.lang.lisp Subject: references/ideas on writing interpreters/debuggers Keywords: interpreter, debug, lisp, scheme Message-ID: Date: 10 Oct 90 22:04:24 GMT Sender: compilers-sender@esegue.segue.boston.ma.us Reply-To: ham@Neon.Stanford.EDU (Peter R. Ham) Organization: Stanford University Lines: 14 Approved: compilers@esegue.segue.boston.ma.us I have a Scheme system, Scheme->C. I've currently implemented a more "user-friendly", pascalish (much simpler) language on top of this system by translating the user friendly language to scheme. Now, I need to build a debugger for this. I figure that since I'm generating the code, I should be able to make it easy for my debugger to debug. I've seen one reference on this "Debugging Standard ML Without Reverse Engineering". Anybody have any ideas/references on how to do this? The generated code doesn't have to be blazingly fast, I'm just looking for a simple solution to support source level debugging, breakpoints, and variable tracing. -- Peter -- Send compilers articles to compilers@esegue.segue.boston.ma.us {ima | spdcc | world}!esegue. Meta-mail to compilers-request@esegue.