public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Analysis of solaris2 27_io/istream_extractor_arith.cc failures
Date: Thu, 26 Dec 2002 19:16:00 -0000	[thread overview]
Message-ID: <m3adiszvb6.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <200212261347.IAA14641@caip.rutgers.edu>

"Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> writes:

[...]

| I'd like to chop out the particular code (test12) into a new file and
| xfail just that test.

I believe that is a sensible approach.

[...]

| Patch to follow after some testing.  Any suggestions for the name of
| the new split out file?  Using istream_extractor_arith2 didn't seem
| very descriptive.

Well, I'm not sure we will come up with a naming scheme that is
  a) sensical, i.e. descriptive;
  b) matches standard description. i.e. the paragraph in the Standard;
     specificationp;
  c) scalable;
  d) easy to use.

I suspect that, somehow, we will end up with numbers.  Therefore I
would suggest the testcases be named after the title of the
paragraphes that describe them in the C++ definition text.  I know
Benjamin is skeptical about numbering, so I would appreciate to have
his input on this suggestion.

-- Gaby

  reply	other threads:[~2002-12-26 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26 17:51 Kaveh R. Ghazi
2002-12-26 19:16 ` Gabriel Dos Reis [this message]
2002-12-26 21:56   ` Kaveh R. Ghazi
2003-01-04 14:56     ` Kaveh R. Ghazi
2003-01-05  1:55     ` Benjamin Kosnik
2003-01-05  2:18       ` Gabriel Dos Reis
2003-01-05  4:57         ` Benjamin Kosnik
2003-01-05  6:31       ` Kaveh R. Ghazi
2003-01-05 11:19         ` Phil Edwards
2003-01-05 19:36           ` Kaveh R. Ghazi
2003-01-06  4:38           ` Kaveh R. Ghazi
2003-01-06  5:18             ` Benjamin Kosnik

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=m3adiszvb6.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    --cc=libstdc++@gcc.gnu.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).