Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: List Manager Problem
Keywords: combining text and graphics.
Message-ID: <900@husc6.harvard.edu>
Date: 1 Jan 89 18:28:45 GMT
References: <221@dalcsug.UUCP> <966@geowhiz.UUCP> <1235@viscous> <896@husc6.harvard.edu> <66569@ti-csl.CSNET>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec/THINK Technologies, Bedford, MA
Lines: 23

In article <66569@ti-csl.CSNET> holland@m2.UUCP (Fred Hollander) writes:
>tip.  But, don't tell me (it would be too good to be true) that you can
>now debug the defproc at source level.

	In fact, you can. LDEFs are quite easy to debug. Other defprocs
that are event-driven, such as CDEFs and MDEFs, can also be debugged
at the source level. Unfortunately, you can't debug WDEFs at the source level,
because of some tricks that the debugger pulls; however, you can embed
them in your program the same as any other defproc.

		--Rich



Rich Siegel
Staff Software Developer
THINK Technologies Division, Symantec Corp.
Internet: siegel@endor.harvard.edu
UUCP: ..harvard!endor!siegel
Phone: (617) 275-4800 x305

Any opinions stated in this article do not necessarily reflect the views
or policies of Symantec Corporation or its employees.