public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "David Abrahams" <david.abrahams@rcn.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/3759: nonconforming use of unqualified std:: names Date: Thu, 26 Jul 2001 06:36:00 -0000 [thread overview] Message-ID: <20010726133600.15184.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/3759; it has been noted by GNATS. From: "David Abrahams" <david.abrahams@rcn.com> To: "Gabriel Dos Reis" <gdr@codesourcery.com> Cc: "Gabriel Dos Reis" <gdr@codesourcery.com>, <rittle@labs.mot.com>, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: libstdc++/3759: nonconforming use of unqualified std:: names Date: Thu, 26 Jul 2001 09:23:59 -0400 ----- Original Message ----- From: "Gabriel Dos Reis" <gdr@codesourcery.com> > "David Abrahams" <david.abrahams@rcn.com> writes: > | > | Loren's email doesn't seem to be concerned with the issue of whether the > | library meets the spec, but with general GNU coding style guidelines in > | which (I think) I have no stake. > > No. I don't think you undertand Loren's mail correectly. As I > understand Loren's mail, the issue isn't just about GNU coding style > -- he used elements from that coding style to justify qualification. > His concerns, as I undertand it, is to come with a solution To what? I'm not being (intentionally) obtuse here; it seems like he and you are concerned with the use of explicit qualification. In the context of this discussion, I am only concerned with getting the library to meet its spec. Since there are other ways to do that than adding explicit qualification, it doesn't seem like there's much for me to contribute to the discussion the two of you want to have... unless I misunderstand something. > and an additional "guiding principles" to the existing coding style. As I wrote, I don't think I have a stake in that part of the discussion. > | I wasn't planning to respond, but if you > | think there is a point that merits my direct attention, please forward me > | the excerpt in question. > > I don't know exactly how I'm supposed to behave in face of such a > condescending tone. Wow, we really got off on the wrong foot here. I didn't mean to be condescending. Maybe "merits" isn't the best word and I should have said "warrants". In any case, I'm just trying to say that I don't think I can add anything more useful to the discussion than I already have, and I didn't notice any new opportunities for me to be helpful in Loren's message. If you did, I'd like you to point me at them so I can try. Otherwise, I think, as they say, "my work here is done". -Dave
next reply other threads:[~2001-07-26 6:36 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-26 6:36 David Abrahams [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-07-26 6:26 Gabriel Dos Reis 2001-07-26 6:16 David Abrahams 2001-07-26 5:56 Gabriel Dos Reis 2001-07-26 5:46 David Abrahams 2001-07-25 15:46 Gabriel Dos Reis 2001-07-25 15:36 David Abrahams 2001-07-25 14:56 Gabriel Dos Reis 2001-07-25 14:16 Loren James Rittle 2001-07-24 11:26 Gabriel Dos Reis 2001-07-24 11:06 Gabriel Dos Reis 2001-07-24 10:46 Gabriel Dos Reis 2001-07-24 10:36 David Abrahams 2001-07-24 10:16 Gabriel Dos Reis 2001-07-24 10:06 David Abrahams 2001-07-24 9:36 Gabriel Dos Reis 2001-07-23 16:23 ljrittle 2001-07-21 11:36 david.abrahams
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=20010726133600.15184.qmail@sourceware.cygnus.com \ --to=david.abrahams@rcn.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).