This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
template behavior
- From: Al Niessner <Al dot Niessner at jpl dot nasa dot gov>
- To: list gcc <gcc-help at gcc dot gnu dot org>
- Date: Tue, 16 Nov 2004 08:53:58 -0800
- Subject: template behavior
- Organization: Jet Propulsion Laboratory
Has template behavior changed because I could not find a matching
changing in the change log at gcc.gnu.org?
I have code (octave-forge source to be specific) which contains the line
template std::map<std::string,std::string>;
and compiles just fine with gcc < 3.4.1 && gcc > 3.2. To get it
compiling and working with gcc 3.4.1, I had to #ifdef that line away
with the 3.4 series of compilers. I then searched the change log for
something that would indicate this behavioral change and did not see it
-- does not mean it is not there but rather that I did not find it with
my searches and quick scanning. So did something change in gcc that I
missed or is my compiler non compliant with the standard?
--
Al Niessner <Al.Niessner@jpl.nasa.gov>
Jet Propulsion Laboratory
All opinions stated above are mine and do not necessarily reflect
those of JPL or NASA.
----
| dS | >= 0
----