From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: "m." <michal017@centrum.sk>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: c++ STL change?
Date: Mon, 10 Nov 2003 14:38:00 -0000 [thread overview]
Message-ID: <871xsgjnkg.fsf@student.uni-tuebingen.de> (raw)
In-Reply-To: <20031110150448.4f68f76d.michal017@centrum.sk>
"m." <michal017@centrum.sk> writes:
> I am using STL classes with gcc and I noticed a change between 3.3.2 and
> 3.2.2 versions in the std::map class implementation.
>
> The typename for value type in map differs:
> 3.3.2 = mapped_type
> 3.2.2 = data_type
> (as seen in c++/3.x.x/bits/stl_map.h file).
>
> I am using STL manual from http://www.sgi.com/tech/stl/Map.html which
> says it should be data_type as it is in the 3.2.2 version.
> Can anyone explain this?
The C++ standard uses mapped_type; the SGI STL predates the standard.
--
Falk
next prev parent reply other threads:[~2003-11-10 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 14:06 m.
2003-11-10 14:38 ` Falk Hueffner [this message]
2003-11-10 14:37 Lev Assinovsky
2003-11-11 18:13 lrtaylor
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=871xsgjnkg.fsf@student.uni-tuebingen.de \
--to=falk.hueffner@student.uni-tuebingen.de \
--cc=gcc-help@gcc.gnu.org \
--cc=michal017@centrum.sk \
/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).