Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!tank!gargoyle!chinet!patrickd
From: patrickd@chinet.chi.il.us (Patrick Deupree)
Newsgroups: comp.windows.ms
Subject: Re: ACTOR debugging
Message-ID: <1990Jun7.193817.1556@chinet.chi.il.us>
Date: 7 Jun 90 19:38:17 GMT
References: <292600009@trsvax>
Organization: The Whitewater Group, Evanston, IL
Lines: 25

In article <292600009@trsvax> reyn@trsvax.UUCP writes:
>Does ACTOR allow you to create DLL's?
No, but it allows you to access existing DLL's.

>If so, do they supply a debugger which allows you to debug them at the
>source code level?
We supply a debugger that allows you to debug Actor source code.  This
debugger will allow you to see the source, inspect the variables, and you
can also change the source code, compile it, then go back to the application.

Just to clear one thing up, Actor is an incrementally compiled language
that is created, modified, and run in a development environment within windows.
We usually call Actor a development system, not a development language.

>Does ACTOR produce symbol tables which will work with SYMDEB?
Since Actor is not compiled but incrementatally compiled, we don't produce
symbol tables.  Well, we don't produce anything like what SYMDEB uses.
However, the Actor executable that is distributed can be run
with codeview or a tracing mechanism we provide for debugging purposes.

-- 
"Organized fandom is composed of a bunch of nitpickers with a thing for
 trivial pursuit."  -Harlan Ellison

Patrick Deupree ->	patrickd@chinet.chi.il.us