Problem with enums and std::max()

[Hendrik Schober]

Hi,

consider this:

#include <algorithm>

enum X { foo, bar };

int main()
{
std::max( foo, bar );
return 0;
}

GCC 3.3.5 (with Dinkumware's std lib) warns that a reference
to a local object is returned in the above code. Neither VC8
nor XCode2's GCC (both with Dinkumware, too) complain about
this code. Am I right in supposing that this is simply a bug
in GCC 3.3.5?

TIA,

Schobi

--
(e-mail address removed) is never read
I'm Schobi at suespammers dot org

"The sarcasm is mightier than the sword."
Eric Jarvis

 

[mlimber]

consider this:

#include <algorithm>

enum X { foo, bar };

int main()
{
std::max( foo, bar );
return 0;
}

GCC 3.3.5 (with Dinkumware's std lib) warns that a reference
to a local object is returned in the above code. Neither VC8
nor XCode2's GCC (both with Dinkumware, too) complain about
this code. Am I right in supposing that this is simply a bug
in GCC 3.3.5?

Likely. EDG, VC6, and MINGW (gcc version something-or-other at
Dinkumware.com) don't complain either.

Cheers! --M

 

[Hendrik Schober]

consider this:
[...] Am I right in supposing that this is simply a bug
in GCC 3.3.5?

Likely. EDG, VC6, and MINGW (gcc version something-or-other at
Dinkumware.com) don't complain either.

Thanks for looking into this!

Cheers! --M

Schobi

--
(e-mail address removed) is never read
I'm Schobi at suespammers dot org

"The sarcasm is mightier than the sword."
Eric Jarvis