From: Daniel Berlin <dberlin@dberlin.org>
To: David Carlton <carlton@math.stanford.edu>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] handling of 'operator' in cp_find_first_component
Date: Thu, 24 Apr 2003 01:13:00 -0000 [thread overview]
Message-ID: <DC473B69-75E5-11D7-86C5-000A95A34564@dberlin.org> (raw)
In-Reply-To: <ro1znmgeqwo.fsf@jackfruit.Stanford.EDU>
On Wednesday, April 23, 2003, at 07:27 PM, David Carlton wrote:
> On Tue, 22 Apr 2003 10:33:05 -0400, Daniel Berlin
> <dberlin@dberlin.org> said:
>
>> To answer whether you need the return type, let's add two
>> specializations here and make it worse:
>
>> template <> long foo (int a)
>> {
>> return 9;
>> }
>> template <> int foo (int a)
>> {
>> return 10;
>> }
>
> Yeah, but that's illegal, isn't it? You can't have two functions that
> differ only in return type: otherwise, how would the compiler know
> which one to use in a call to foo?
>
> I tried it out in GCC; the above doesn't compile (I guess templates
> with 0 parameters aren't legal),
It's not a template, it's a specialization, i just didn't paste the
right thing.
template <> int foo<int> (int a)
{
return 5;
}
template <> long foo<long> (int a)
{
return 9;
}
is what that should be.
You can have two templates that only differ in return type, and they
become, when instantiated, two functions that only differ in return
type.
--Dan
next prev parent reply other threads:[~2003-04-23 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 19:17 David Carlton
2003-04-18 19:47 ` Daniel Berlin
2003-04-22 3:21 ` Daniel Jacobowitz
2003-04-22 15:09 ` Daniel Berlin
2003-04-22 15:23 ` Daniel Jacobowitz
2003-04-23 23:46 ` David Carlton
2003-04-23 23:49 ` David Carlton
2003-04-24 1:13 ` Daniel Berlin [this message]
2003-04-23 23:45 ` David Carlton
2003-04-24 1:25 ` David Carlton
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=DC473B69-75E5-11D7-86C5-000A95A34564@dberlin.org \
--to=dberlin@dberlin.org \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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