From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,44e43dc2ffe2ab01
X-Google-Attributes: gid103376,public
From: tmoran@bix.com
Subject: Re: Perhaps there _is_ a conspiracy against Ada
Date: 1997/04/24
Message-ID: <5jns4h$hv0@lotho.delphi.com>#1/1
X-Deja-AN: 237065973
Organization: Delphi Internet Services <http://www.delphi.com/>
Newsgroups: comp.lang.ada
Date: 1997-04-24T00:00:00+00:00
List-Id: <comp.lang.ada>


>And just how did you attach callback functions to GUI objects
  You are quite right for the Macintosh where the (Meridian)
compiler supplied a binding to the Mac OS that used their way
of doing things.  But event driven under DOS did not need callbacks,
because DOS didn't use callbacks.  It just had a looping task that
called things (as well as separate tasks for some of the audio+video).

>>  Having the program print something like "Constraint Error, value = -1"
>>and a traceback sure beats setting breakpoints in a program whose bug
>>symptom is a system crash.
>2. I find it faster to add events to debugger breakpoints when I find a
>testing error than to add a bunch of gratuitious print statements
>that I will later have to remove.
  No, the 'print something...' did not mean 'insert print statements'.
The compiler's run-time-system automatically generated those messages
for any unhandled exception.  And (unless you turned off checking) it
inserted exception checking code wherever it needed to.  So nothing was
required of the programmer, and he didn't have to change anything.
If a little speed increase was crucial, you could recompile with
checking off - but hearing from some distant stranger that "the
program died with error X in subroutine Y at line Z" sure beats
"the program died.".