Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!hplabs!otter.hpl.hp.com!otter!adw
From: adw@otter.hpl.hp.com (Dave Wells)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Actor specific questions
Message-ID: <72170004@otter.hpl.hp.com>
Date: 18 Mar 91 16:15:56 GMT
References: <27106@rouge.usl.edu>
Organization: Hewlett-Packard Laboratories, Bristol, UK.
Lines: 34

From: pcb@basin04.cacs.usl.edu (Peter C. Bahrs)
Date: Fri, 15 Mar 1991 07:45:23 GMT
Subject: Actor specific questions
Newsgroups: comp.windows.ms.programmer

>Also in an expression, you may want to negate an object such as a:=4;
>           method(object, -a, 3);  this does not work?  I have
>been using either  minusOne*a  or 0-a   ughhh.

method(object, negate(a), 3);

>And finally, for now, has anyone figured out how to modify the interpreter
>so that when an application does something stupid and the debugger
>comes up, the application will not try to process any more messages?

Not in general. The paint() -> debugger -> paint() -> debugger...
loop can be solved:

Def paint(self, hdc)
{ if frames(Bug)
  then printLine(asString(class(self))+":paint() called, but a Debug window"+
            " was up."
  else
    draw(self,hdc);       /* (or whatever) */
  endif;
}

This seems to allow you to get into the debugger reliably. If you keep
hitting "OK" on the debug dialog, however, ACTOR siezes up after a few more
repaints - cause unknown.

Hope this helps,

Dave Wells