public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: peturr02@ru.is
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/9580: basic_filebuf<> with custom traits_type fails to link
Date: Wed, 05 Feb 2003 10:36:00 -0000	[thread overview]
Message-ID: <20030205103154.28958.qmail@sources.redhat.com> (raw)


>Number:         9580
>Category:       libstdc++
>Synopsis:       basic_filebuf<> with custom traits_type fails to link
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 05 10:36:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     peturr02@ru.is
>Release:        gcc-3.2.1
>Organization:
>Environment:
Red Hat Linux 8.0
>Description:
basic_filebuf<CharT, Traits> fails to link if CharT is any type other than char or wchar_t or if Traits is any type other than char_traits<CharT>.

I think the attached program is required to link and run, in particular it satisfies the requirements for Traits in 21.1.1, 27.1.2 and 27.8.1.1.
>How-To-Repeat:
See attachment.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="instbug.cc"
Content-Disposition: inline; filename="instbug.cc"

#include <fstream>
using namespace std;

class MyTraits : public char_traits<char>
{
};

int main()
{
	basic_filebuf<char, MyTraits> fb;
	return 0;
}


             reply	other threads:[~2003-02-05 10:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 10:36 peturr02 [this message]
2003-02-13 20:11 paolo
2003-02-13 20:56 Gabriel Dos Reis
2003-02-13 21:06 Paolo Carlini
2003-02-13 21:16 Gabriel Dos Reis
2003-02-13 21:21 paolo
2003-02-13 21:26 Paolo Carlini
2003-02-13 21:36 Gabriel Dos Reis
2003-02-13 21:46 Paolo Carlini
2003-02-17 20:10 paolo

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=20030205103154.28958.qmail@sources.redhat.com \
    --to=peturr02@ru.is \
    --cc=gcc-gnats@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).