public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/8616: std::string<double> ?
Date: Fri, 22 Nov 2002 14:27:00 -0000 [thread overview]
Message-ID: <20021118041604.17962.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/8616; it has been noted by GNATS.
From: Phil Edwards <phil@jaj.com>
To: bwheadley@earthlink.net
Cc: gcc-gnats@gcc.gnu.org, nigels@nigels.com
Subject: Re: libstdc++/8616: std::string<double> ?
Date: Sun, 17 Nov 2002 23:14:37 -0500
On Mon, Nov 18, 2002 at 12:57:47AM -0000, bwheadley@earthlink.net wrote:
> >Description:
> std::string<double> j is a valid datatype?
The second foo.log doesn't contain any compiler messages.
In any case, no, this
int main(int argc,char *argv[])
{
std::string<double> j;
// j = 25.9;
}
is not going to work. I'm not even certain what you're trying to do.
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
next reply other threads:[~2002-11-18 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 14:27 Phil Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-23 14:26 bkoz
2002-11-22 13:56 Bryan W. Headley
2002-11-22 13:29 bwheadley
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=20021118041604.17962.qmail@sources.redhat.com \
--to=phil@jaj.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: 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).