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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no 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!postnews.google.com!n59g2000hsh.googlegroups.com!not-for-mail From: "kevin cline" Newsgroups: comp.lang.ada Subject: Re: What is wrong with Ada? Date: 12 Apr 2007 09:44:33 -0700 Organization: http://groups.google.com Message-ID: <1176396273.374929.11360@n59g2000hsh.googlegroups.com> References: <1176150704.130880.248080@l77g2000hsb.googlegroups.com> <461B52A6.20102@obry.net> <461BA892.3090002@obry.net> <82dgve.spf.ln@hunter.axlog.fr> <1176226291.589741.257600@q75g2000hsh.googlegroups.com> <4eaive.6p9.ln@hunter.axlog.fr> NNTP-Posting-Host: 208.8.57.2 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: posting.google.com 1176396273 21159 127.0.0.1 (12 Apr 2007 16:44:33 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 12 Apr 2007 16:44:33 +0000 (UTC) In-Reply-To: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3,gzip(gfe),gzip(gfe) X-HTTP-Via: 1.1 ics_server.swacorp.com (ICS 2.3.0.0.16) Complaints-To: groups-abuse@google.com Injection-Info: n59g2000hsh.googlegroups.com; posting-host=208.8.57.2; posting-account=Thx6EwwAAAAirqf96i7UdETSL0vfyj5f Xref: g2news1.google.com comp.lang.ada:14947 Date: 2007-04-12T09:44:33-07:00 List-Id: On Apr 11, 6:45 pm, Brian May wrote: > >>>>> "Jean-Pierre" == Jean-Pierre Rosen writes: > > Jean-Pierre> My experience is that recompiling (generally a single > Jean-Pierre> body where you added the trace) is much faster than > Jean-Pierre> starting the debugger, setting breakpoints, skipping > Jean-Pierre> lots of unnecessary breaks, and so on. > > Assuming you notice that a bug exists. This is a big problem I have > had especially with most interpreted languages. The only way you can > be sure the code is bug free is too regularly test every possible > path, including different error conditions. This is also true of compiled languages. The compiler can not detect all errors, so you still have to test every possible path, including different error conditions. > Otherwise you find that > after a minor but unexpected error condition your previously working > code calls display__error() instead of display_error() and it becomes > a fatal function-not-found error (even if you swear: I didn't change > that line!). Or you could discover that after an unexpected condition the resulting exception is not caught, and the program exits instead of recovering. > -- > Brian May