public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: lerdsuwa@gcc.gnu.org To: lerdsuwa@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/186 Date: Sat, 26 May 2001 00:46:00 -0000 [thread overview] Message-ID: <20010526074600.3016.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/186; it has been noted by GNATS. From: lerdsuwa@gcc.gnu.org To: gcc-gnats@gcc.gnu.org, heiko.goller@gmx.net, lerdsuwa@gcc.gnu.org, martin@loewis.home.cs.tu-berlin.de, nobody@gcc.gnu.org Cc: Subject: Re: c++/186 Date: 26 May 2001 07:37:59 -0000 Synopsis: bug report: explicit template instantiation Responsible-Changed-From-To: unassigned->lerdsuwa Responsible-Changed-By: lerdsuwa Responsible-Changed-When: Sat May 26 00:37:59 2001 Responsible-Changed-Why: Patch submitted. The code is illegal though as the template specialization string_char_traits<char> already exists in <std/straits.h>. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=186&database=gcc
next reply other threads:[~2001-05-26 0:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-26 0:46 lerdsuwa [this message] 2001-05-26 12:06 c++/186 Martin Sebor
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=20010526074600.3016.qmail@sourceware.cygnus.com \ --to=lerdsuwa@gcc.gnu.org \ --cc=gcc-prs@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).