exception and polymorphism problem

[josh]

Hi I have this code:

class Exception : public exception
{
public:
Exception(strin g m="exception! ") : msg(m) {}
~Exception() throw() {}
const char* what() { return msg.c_str(); }

private:
string msg;
};

int main()
{
try
{
throw Exception();
}
catch(exception e)
{
cout << e.what() << endl;
}

return 0;
}

when I run it I don't have print out my message "exception! " but
St9exception

why?

[=?iso-8859-1?q?Erik_Wikstr=F6m?=]

On 16 Maj, 13:01, josh <xdevel1...@gma il.comwrote:

Hi I have this code:

class Exception : public exception
{
public:
Exception(strin g m="exception! ") : msg(m) {}
~Exception() throw() {}
const char* what() { return msg.c_str(); }

private:
string msg;

};

int main()
{
try
{
throw Exception();
}
catch(exception e)
{
cout << e.what() << endl;
}

return 0;

}

when I run it I don't have print out my message "exception! " but
St9exception

Because you catch the exception by value, so you copy-construct a new
std::exception from the Exception that was thrown, catch the exception
by reference instead and it will work:

catch (exception& e)

--
Erik Wikström

[mimi]

On 5ÔÂ16ÈÕ, ÏÂÎç7ʱ01·Ö, josh <xdevel1...@gma il.comwrote:

Hi I have this code:

class Exception : public exception
{
public:
Exception(strin g m="exception! ") : msg(m) {}
~Exception() throw() {}
const char* what() { return msg.c_str(); }

private:
string msg;

};

int main()
{
try
{
throw Exception();

An exception object is always created at the throw point.We reference
it as "temp" here.

}
catch(exception e)

The exception declaration of a catch clause behaves very much like a
parameter declaration. Here, e is another object of type exception
(Not Exception) that initialized by the "temp" of type Exception.

{
cout << e.what() << endl;

So, here, the e.what() refers to the what() member function of class
Exception, but not class exception.

}

return 0;

}

when I run it I don't have print out my message "exception! " but
St9exception

why?

[josh]

On 16 Mag, 13:04, Erik Wikström <eri...@student .chalmers.sewro te:

On 16 Maj, 13:01, josh <xdevel1...@gma il.comwrote:

Hi I have this code:

class Exception : public exception
{
public:
Exception(strin g m="exception! ") : msg(m) {}
~Exception() throw() {}
const char* what() { return msg.c_str(); }

private:
string msg;

};

int main()
{
try
{
throw Exception();
}
catch(exception e)
{
cout << e.what() << endl;
}

return 0;

}

when I run it I don't have print out my message "exception! " but
St9exception

Because you catch the exception by value, so you copy-construct a new
std::exception from the Exception that was thrown, catch the exception
by reference instead and it will work:

catch (exception& e)

--
Erik Wikström

yes I've forgotten that...... so it print 9Exception but not
my msg string may be I didn't override the right what() ?

P.S.
I try to read the source of exception.h and exception.cpp but in my
gcc source I didn't find it!
where are them?

[Zeppe]

josh wrote:

>
yes I've forgotten that...... so it print 9Exception but not
my msg string may be I didn't override the right what() ?

no, you did. the problem, as Eric said, is that if you don't put the
reference a new std::exception is created by copy-constructor. And for
the standard exception the what behaves differently that for your class.

P.S.
I try to read the source of exception.h and exception.cpp but in my
gcc source I didn't find it!
where are them?

it depends. For me, /usr/include/c++/4.1.2/exception

Regards,

Zeppe

[josh]

On 16 Mag, 13:49, Zeppe <zeppe@.remove. all.this.long.c omment.email.it >
wrote:

josh wrote:

yes I've forgotten that...... so it print 9Exception but not
my msg string may be I didn't override the right what() ?

no, you did. the problem, as Eric said, is that if you don't put the
reference a new std::exception is created by copy-constructor. And for
the standard exception the what behaves differently that for your class.

P.S.
I try to read the source of exception.h and exception.cpp but in my
gcc source I didn't find it!
where are them?

it depends. For me, /usr/include/c++/4.1.2/exception

Regards,

Zeppe

I do it but still the code doesn't work.

....

try
{
throw Exception();
}
catch(exception &e)
{
cout << e.what() << endl;
}
....

here e is a reference to the new Exception() created so
at run-time e.what() should point to my Exception class
and to print "exception! " but it doesn't do that and print
9Exception ... why?

[Markus Moll]

Hi

Zeppe wrote:

josh wrote:

>yes I've forgotten that...... so it print 9Exception but not
my msg string may be I didn't override the right what() ?

no, you did. the problem, as Eric said, is that if you don't put the
reference a new std::exception is created by copy-constructor. And for
the standard exception the what behaves differently that for your class.

No, he did not. In std::exception it is
virtual const char* what() const throw();

So it should read:

class Exception : public exception
{
public:
Exception(strin g m="exception! ") : msg(m) {}
~Exception() throw() {}
const char* what() const throw () { return msg.c_str(); }

private:
string msg;
};

The const is part of the function signature and thus necessary for
overriding while without the throw() part the program would be ill-formed.

Markus

[Zeppe]

Markus Moll wrote:

Hi

Zeppe wrote:

>josh wrote:

>>yes I've forgotten that...... so it print 9Exception but not
my msg string may be I didn't override the right what() ?

no, you did. the problem, as Eric said, is that if you don't put the
reference a new std::exception is created by copy-constructor. And for
the standard exception the what behaves differently that for your class.

No, he did not.

Damn lunch break! I know I should have checked before sending, but I was
hungry... :)

Sorry guys

Regards,

Zeppe

[josh]

On 16 Mag, 14:05, Markus Moll <markus.m...@es at.kuleuven.bew rote:

Hi

Zeppe wrote:

josh wrote:

yes I've forgotten that...... so it print 9Exception but not
my msg string may be I didn't override the right what() ?

no, you did. the problem, as Eric said, is that if you don't put the
reference a new std::exception is created by copy-constructor. And for
the standard exception the what behaves differently that for your class.

No, he did not. In std::exception it is
virtual const char* what() const throw();

So it should read:

class Exception : public exception
{
public:
Exception(strin g m="exception! ") : msg(m) {}
~Exception() throw() {}
const char* what() const throw () { return msg.c_str(); }

private:
string msg;

};

The const is part of the function signature and thus necessary for
overriding while without the throw() part the program would be ill-formed.

Markus

yes that was my wrong (and also to make Exception not a reference) now
it works!!!

[James Kanze]

On May 16, 1:04 pm, Erik Wikström <eri...@student .chalmers.sewro te:

On 16 Maj, 13:01, josh <xdevel1...@gma il.comwrote:

Hi I have this code:

class Exception : public exception
{
public:
Exception(strin g m="exception! ") : msg(m) {}
~Exception() throw() {}
const char* what() { return msg.c_str(); }

private:
string msg;
};

int main()
{
try
{
throw Exception();
}
catch(exception e)
{
cout << e.what() << endl;
}
return 0;
}

when I run it I don't have print out my message "exception! " but
St9exception

Because you catch the exception by value, so you copy-construct a new
std::exception from the Exception that was thrown, catch the exception
by reference instead and it will work:

catch (exception& e)

Just a detail, but he's probably not going to be modifying the
object, so:
catch ( exception const& e )
would be more appropriate. (In practice, in the case of
exceptions, I don't think it makes much difference, but using
const systematically when appropriate is a good habit to get
into.)

--
James Kanze (Gabi Software) email: ja*********@gma il.com
Conseils en informatique orientée objet/
Beratung in objektorientier ter Datenverarbeitu ng
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]