public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Geert Bosch <bosch@gnat.com>
Cc: guerby@acm.org, gcc@gcc.gnu.org
Subject: Re: ACATS legal status cleared by FSF
Date: Thu, 06 Dec 2001 18:22:00 -0000	[thread overview]
Message-ID: <20011207021249.GC25764@codesourcery.com> (raw)
In-Reply-To: <A04E151A-EAA2-11D5-8627-00039344BF4A@gnat.com>

On Thu, Dec 06, 2001 at 06:40:27PM -0500, Geert Bosch wrote:
> 
> Yes, I'm confident it does too. That is why I am in favor of adding
> these tests and running them. Of all the Ada cases you're talking about,
> there has not even been one that was related to a B test. They are
> completely useless for testing the backend and almost useless for 
> the front end.

My experience working on the C front end has been that tests for proper
diagnostics from ill-formed code are extremely useful.  Can you explain
why they're almost useless for the Ada front end?

> I think it is important to realize, that it is easy enough to go and
> add B tests later on, if you find they would have caught problems that
> went by unnoticed. The tests are available and can be added at any time.
> Paying a high upfront price to prevent this scenario that the Ada
> maintainers find unlikely to be a problem, seems not a good idea to me.
> The only thing it will do is hinder development.

This is all fair.  How about a compromise position where you check the B
tests into the CVS tree but don't bother adding dejagnu harnesses for them.
They are then instantly available if they are needed.

zw

  reply	other threads:[~2001-12-07  2:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 15:13 guerby
2001-12-05 16:21 ` Joseph S. Myers
2001-12-05 18:00 ` Jerry van Dijk
2001-12-06  3:36 ` Geoff Keating
2001-12-06  9:34 ` Geert Bosch
2001-12-06 11:48   ` Zack Weinberg
2001-12-06 14:24     ` Geert Bosch
2001-12-06 14:32       ` Joseph S. Myers
2001-12-06 15:10       ` Zack Weinberg
2001-12-06 15:41         ` Geert Bosch
2001-12-06 18:22           ` Zack Weinberg [this message]
2001-12-05 15:28 Richard Kenner
2001-12-05 15:41 ` guerby
2001-12-05 23:36 dewar
2001-12-06 15:01 Richard Kenner
2001-12-06 15:40 Richard Kenner
2001-12-06 17:38 dewar
2001-12-06 19:09 dewar
2001-12-07  3:18 Richard Kenner
2001-12-07 17:59 dewar
2001-12-07 18:50 mike stump
2001-12-07 18:57 dewar
2001-12-07 19:12 dewar
2001-12-09 13:02 ` Zack Weinberg
2001-12-09 14:52   ` guerby
2001-12-09 19:47     ` Geert Bosch
2001-12-09 14:00 dewar
2001-12-09 15:06 dewar
2001-12-09 15:55 ` Joseph S. Myers
2001-12-09 19:03 dewar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011207021249.GC25764@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=bosch@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=guerby@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).