Path: utzoo!attcan!uunet!lll-winken!lll-tis!mordor!joyce!ames!think!bloom-beacon!mit-eddie!uw-beaver!fluke!mce
From: mce@tc.fluke.COM (Brian McElhinney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: LSC almost gets it right.
Message-ID: <5154@fluke.COM>
Date: 12 Sep 88 20:08:00 GMT
References: <5077@fluke.COM> <526@bruce.oz> <5125@fluke.COM> <326@husc6.harvard.edu>
Sender: news@tc.fluke.COM
Organization: SRS Recursive Software, Castrovalva, WA
Lines: 22

In article <326@husc6.harvard.edu> singer@endor.UUCP (Rich Siegel) writes:
>	As documented, if you hold down the mouse button on the current
>function name, a popup menu gives you the call chain, and selecting an
>item from this menu takes you to that procedure. (Assuming, of course, that
>you've compiled that procedure with debug tables in.))

Sorry, I wasn't being clear enough.  I'm aware of that feature, but you can't
get to the complete stack frame.  You cannot look at the related parameters,
or local variables, for that line of code (that's what I meant by stack frame;
the PC is only one part of it).

Another feature I would love to see implemented is known in the UNIX world as
tags (the ctags program).  It would allow you to, say, double click on a
symbol and be taken to it's definition in the source code.

There are many other features on my wish list (two views of the same source
file, smart indentation, better integration with the debugger, etc.), but full
stack frames and tags would make the most improvement in the LSC programming
environment.


Brian McElhinney
mce@tc.fluke.com