public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: 158988@bugs.debian.org
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/9066: docs for char_traits template not having an implementation
Date: Fri, 27 Dec 2002 08:06:00 -0000 [thread overview]
Message-ID: <20021227155814.31901.qmail@sources.redhat.com> (raw)
>Number: 9066
>Category: libstdc++
>Synopsis: docs for char_traits template not having an implementation
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Fri Dec 27 08:06:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: 158988@bugs.debian.org
>Release: 3.2 branch
>Organization:
>Environment:
>Description:
[from http://bugs.debian.org/158988]
On Sat, Aug 31, 2002 at 04:07:36PM -0400, Phil Edwards wrote:
> On Sat, Aug 31, 2002 at 02:17:45PM +0200, Tobias Hunger wrote:
> > This
> > is very annoying as you need to fill in all the gory details if you want
> > to have a string of something else (like string<size_t> to hold a list
>
> Well, yeah. "all the gory details" /depend/ on the type you choose;
> they cannot be guessed by a default implementation.
I should add that the recent August archives of the libstdc++ list
(gcc.gnu.org) have examples of how to do the gory details. They will
be formalized into note in the online docs as soon as someone (read: me)
has the time, and possibly may be coded into an <ext/something> header.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-12-27 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 8:06 158988 [this message]
2002-12-27 14:43 pme
2002-12-27 14:46 Phil Edwards
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=20021227155814.31901.qmail@sources.redhat.com \
--to=158988@bugs.debian.org \
--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).