From: Gabriel Dos Reis <gdr@cs.tamu.edu>
To: Joe Buck <Joe.Buck@synopsys.COM>
Cc: Mark Mitchell <mark@codesourcery.com>,
"Steven L. Zook" <SLZook@Qualstar.com>,
gcc@gcc.gnu.org
Subject: Re: Nested Functions in C++
Date: Sat, 23 Oct 2004 15:10:00 -0000 [thread overview]
Message-ID: <m3y8hy82cn.fsf@merlin.cs.tamu.edu> (raw)
In-Reply-To: <20041022123000.A22016@synopsys.com>
Joe Buck <Joe.Buck@synopsys.COM> writes:
[...]
| Consider a feature like the new use of "auto", championed by Bjarne
| himself.
If things go well, we may have to vote for inclusion in the working
paper in 6 months (the decltype part may have to wait another 6 months).
| There appear to be some details that have not yet been worked
| out, but maybe the best way to iron out the remaining issues is to have
| a trial implementation to play with.
|
| This is the one that lets you write
|
| func (std::multimap<std::string, std::string>& amap, std::string key) {
|
| auto iter_pair = amap.equal_range(key);
| ...
| }
|
| instead of
|
| func (std::multimap<std::string, std::string>& amap, std::string key) {
|
| std::pair<std::multimap<std::string, std::string>::iterator,
| std::multimap<std::string, std::string>::iterator>
| iter_pair = amap.equal_range(key);
| ...
| }
|
| I want that! I wanted it years ago.
And it was implemented in Cfront as early as 1983; it was removed, when
some users considered it to be going too far. Seems like we're back
to the future :-)
-- Gaby
next prev parent reply other threads:[~2004-10-23 4:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 4:11 Steven L. Zook
2004-10-22 19:04 ` Mark Mitchell
2004-10-23 0:43 ` Joe Buck
2004-10-23 15:10 ` Gabriel Dos Reis [this message]
2004-10-23 16:17 ` Joe Buck
2004-10-23 13:52 ` Gabriel Dos Reis
2004-10-23 16:54 ` Andrew Haley
2004-10-23 16:58 ` Steven Bosscher
2004-10-24 11:35 ` Andrew Haley
2004-10-24 12:01 ` Robert Dewar
2004-10-24 18:05 ` Gabriel Dos Reis
2004-10-24 18:08 ` Robert Dewar
2004-10-24 18:51 ` Gabriel Dos Reis
2004-10-24 3:29 ` Robert Dewar
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=m3y8hy82cn.fsf@merlin.cs.tamu.edu \
--to=gdr@cs.tamu.edu \
--cc=Joe.Buck@synopsys.COM \
--cc=SLZook@Qualstar.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).