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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,93a8020cc980d113
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!proxad.net!213.200.89.82.MISMATCH!tiscali!newsfeed1.ip.tiscali.net!news.tiscali.de!news.belwue.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Newsgroups: comp.lang.ada
Subject: Re: What is wrong with Ada?
From: Georg Bauhaus <bauhaus@futureapps.de>
In-Reply-To: <4eaive.6p9.ln@hunter.axlog.fr>
References: <1176150704.130880.248080@l77g2000hsb.googlegroups.com>
	 <zyBSh.44138$oV.14776@attbi_s21>   <461B52A6.20102@obry.net>
	 <awirc4gv13.fsf@hod.lan.m-e-leypold.de>   <461BA892.3090002@obry.net>
	 <yeabxgnsrj.fsf@hod.lan.m-e-leypold.de>   <82dgve.spf.ln@hunter.axlog.fr>
	 <1176226291.589741.257600@q75g2000hsh.googlegroups.com>
	 <4eaive.6p9.ln@hunter.axlog.fr>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: #
Message-ID: <1176290442.5634.18.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.1 
Date: Wed, 11 Apr 2007 13:20:42 +0200
NNTP-Posting-Date: 11 Apr 2007 12:19:14 CEST
NNTP-Posting-Host: ced260d1.newsspool4.arcor-online.net
X-Trace: 
 DXC=Y1V>C2]H9@YcHPTNZh_e7Q4IUK<Cl32<Q4Fo<]lROoRQ4nDHegD_]RUXH?BSL2;F<RA:ho7QcPOVSKAK\bb6nZ<UY1oj<=iK22\
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:14906
Date: 2007-04-11T12:19:14+02:00
List-Id: <comp.lang.ada>

On Wed, 2007-04-11 at 11:40 +0200, Jean-Pierre Rosen wrote:

> > and it is much easier to trace through
> > the algorithm step by step (using conditional breaks when necessary).

Having a trace of the steps helps (my) understanding, though.

> My experience is that recompiling (generally a single body where you 
> added the trace) is much faster than starting the debugger, setting 
> breakpoints, skipping lots of unnecessary breaks, and so on.

Depending on the debugger, conditional breaks etc etc can be
packaged as a debugger procedure, and the program reloaded
without restarting the debugger. Ok, this doesn't count for
one time tests.