Re: libstdc++/9066: docs for char_traits template not having an implementation

Re: libstdc++/9066: docs for char_traits template not having an implementation

[pme]

Synopsis: docs for char_traits template not having an implementation

Responsible-Changed-From-To: unassigned->pme
Responsible-Changed-By: pme
Responsible-Changed-When: Fri Dec 27 14:43:55 2002
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: open->closed
State-Changed-By: pme
State-Changed-When: Fri Dec 27 14:43:55 2002
State-Changed-Why:
    They've already been written.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9066

Re: libstdc++/9066: docs for char_traits template not having an implementation

[Phil Edwards]

The following reply was made to PR libstdc++/9066; it has been noted by GNATS.

From: Phil Edwards <phil@jaj.com>
To: 158988@bugs.debian.org
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/9066: docs for char_traits template not having an implementation
Date: Fri, 27 Dec 2002 17:42:59 -0500

 On Fri, Dec 27, 2002 at 03:58:14PM -0000, 158988@bugs.debian.org wrote:
 > >Originator:     158988@bugs.debian.org
 
 GAAAH!  Now the braindead BTS will email "info received" messages to
 gcc-gnats, which will file them away as "bug reports I wasn't able to parse,"
 which means somebody will have to go through and weed them all out manually.
 
 Please tell me that the Debian BTS will recognize the gcc-gnats address as
 a special case and not send anything to it automatically.  Or (hint, hint)
 provide a general way for people to /tell/ the BTS, "hey, stop sending me
 the automated crap".
 
 Annoyingly, there's no easy documented way to add oneself to the list of
 recipients of an existing BTS number, and there's no way to remove oneself
 from getting junk from the BTS itself.
 
 
 > On Sat, Aug 31, 2002 at 04:07:36PM -0400, Phil Edwards wrote:
 > 
 > 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.
 
 That's been done:  http://gcc.gnu.org/onlinedocs/libstdc++/21_strings/howto.html#5
 

libstdc++/9066: docs for char_traits template not having an implementation

[158988]

>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: