Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: LSC 3.0 Questions/Comments
Keywords: LSC 3.0
Message-ID: <1680@husc6.harvard.edu>
Date: 24 Apr 89 00:04:37 GMT
References: <13630@steinmetz.ge.com>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec/THINK Technologies, Bedford, MA
Lines: 31

In article <13630@steinmetz.ge.com> leue@crd.ge.com writes:
>
>1. Is there any way to get a text assembler listing of the code that is
>generated?  I would like to use the LSC code as a starting point for

	No. You might consider writing assembler from scratch, using the
inline assembler.

>2. Is there a better way to examine structs in the debugger?  I find
>the data window pretty klunky compared to, say, Sun's DBXTool. If you're
>trying to follow a linked list of structs, you have to keep opening and
>closing individual data windows, and it takes about 4 steps to view
>each new struct.  Perhaps I'm missing something obvious.

	You can always type an expression in the data window which would
evaluate to the structure at the end of the chain you're following. You'll
get a scalar value or a "struct 0x$$$$$$" which you can then double-click
on.

		--Rich

~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

 "She told me to make myself comfortable, so I pulled down my pants
 and sat in the pudding." -Emo Phillips
~~~~~~~~~~~~~~~