[E-Lang] Debugging E programs

[Norman Hardy]

At 14:36 -0400 01/07/06, Jonathan A Rees wrote:
>[At Mark M's request I am re-sending to e-lang some questions that I
>had sent to him and Mark S privately.  To promote better threading I'm
>sending them separately instead of batched as I had originally done.]
>
>What is the current position on debugging?  That is -- is it
>anticipated that there will be anything beyond explicit user-written
>methods and insertion of "print statements" to help track what's going
>on in a vat, set of objects, or other kind of arena?  I could imagine,
>for example, a special super-user capability that allowed the
>debugging entity to get back-door access to internals of all objects
>in a vat.  It sounds horribly wrong, and surely one could do better,
>but what exactly are the alternatives?
>
>If this has been discussed on e-lang in the past, please send me a
>reference to the appropriate place in the mail archive.

I describe our hard-nosed attitude towards debugging with abstraction 
in place here:
<http://cap-lore.com/CapTheory/KK/Debug.html>.
-- 
Norman Hardy  <http://cap-lore.com/>