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.1 required=5.0 tests=BAYES_00,
	PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,d5b211b0c1ffcf3e
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII
Received: by 10.68.234.38 with SMTP id ub6mr4555357pbc.2.1340394958311;
        Fri, 22 Jun 2012 12:55:58 -0700 (PDT)
MIME-Version: 1.0
Path: 
 l9ni7981pbj.0!nntp.google.com!news2.google.com!goblin1!goblin3!goblin.stu.neva.ru!gegeweb.org!news.ecp.fr!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Practicalities of Ada for app development
Date: Fri, 22 Jun 2012 14:55:52 -0500
Organization: Jacob Sparre Andersen Research & Innovation
Message-ID: <js2ikc$a5t$1@munin.nbi.dk>
References: 
 <79c5c9f7-4b72-4990-8961-b3e2db4db79b@qz1g2000pbc.googlegroups.com>
 <jqtr7u$3r9$1@adenine.netfront.net>
 <f33223ab-5c08-40f5-b0ee-a57862ce72f5@googlegroups.com>
 <jqur16$teu$1@adenine.netfront.net> <jrvkq7$qc8$1@munin.nbi.dk>
 <afa4c8e4-dba8-460c-877b-a848255c4572@googlegroups.com>
 <js021v$dul$1@munin.nbi.dk> <js032p$n1t$1@dont-email.me>
NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net
X-Trace: munin.nbi.dk 1340394957 10429 69.95.181.76 (22 Jun 2012 19:55:57 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Fri, 22 Jun 2012 19:55:57 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-RFC2646: Format=Flowed; Original
Date: 2012-06-22T14:55:52-05:00
List-Id: <comp.lang.ada>

"J-P. Rosen" <rosen@adalog.fr> wrote in message 
news:js032p$n1t$1@dont-email.me...
> Le 21/06/2012 23:00, Randy Brukardt a �crit :
>> The only time the debugger hassle is worth it is when the bug is
>> sufficiently low-level that you can't debug it at the Ada level (as when 
>> a
>> register has the wrong value for some reason, causing a hardware fault). 
>> And
>> that usually takes me many hours (usually an entire working day) for a
>> single problem, as opposed to dealing with a problem an hour or so at the
>> Ada level.
> Although I fully agree with you, I can add another use case where a
> debugger can be useful: when you enter an infinite loop and you don't
> have the foggiest idea where it is - assuming that ^C works, which is
> not always the case.

It rarely works usefully on Windows; you usually end up somewhere in the 
kernel and getting back to your program is iffy at best. I do my best to 
avoid writing infinite loops (this is arguably the most important value of 
the iterators in the containers libraries: you can't get an infinite loop 
from using them), but of course you can never be sure. I usually use 
incremental development in small enough steps that there are only one or two 
loops to look at for the problem - so usually the bug is obvious. When it's 
not, I just lose more hair...

                                   Randy.