Do you have experience with exceptions?

[Richard]

[Please do not mail me a copy of your followup]

DeMarcus <[email protected]> spake the secret code

Do you have any favorite sites about test-driven development? I want to
dig even deeper down into that.

Try the Prime Numbers kata by following along my 5-part tutorial on
TDD with C++:
<http://legalizeadulthood.wordpress.com/2009/07/04/c-unit-tests-with-boost-test-part-1/>

 

[gwowen]

What I meant with getters was that if not the what() function takes care
of the data one can provide getters as: getFunctionName(), getLine(),
getFileName(), getErrno(), and maybe getIPAddress() if it's a
NetworkConnectionFailedException.

I have a modest proposal that will satisfy both camps: Store all that
useful information in the .what() string, by encoding it in XML!
There is no computer science mechanism that cannot be improved by
adding a(nother) layer of XML.

 

[DeMarcus]

[Please do not mail me a copy of your followup]

DeMarcus<[email protected]> spake the secret code

Do you have any favorite sites about test-driven development? I want to
dig even deeper down into that.

Try the Prime Numbers kata by following along my 5-part tutorial on
TDD with C++:
<http://legalizeadulthood.wordpress.com/2009/07/04/c-unit-tests-with-boost-test-part-1/>

Thanks!

 

[DeMarcus]

I have a modest proposal that will satisfy both camps: Store all that
useful information in the .what() string, by encoding it in XML!
There is no computer science mechanism that cannot be improved by
adding a(nother) layer of XML.

Actually I've been thinking in those terms since both Windows' and
RFC5424 support structured data in their logs.

Do you know any site showing examples of that so I can get some inspiration?

 

[Ian Collins]

I have a modest proposal that will satisfy both camps: Store all that
useful information in the .what() string, by encoding it in XML!
There is no computer science mechanism that cannot be improved by
adding a(nother) layer of XML.

 

[DeMarcus]

KISS! All the data in the exception is const, so it's public.

Getters (and setters) are evil!

I took a look at C# exceptions and I got quite surprised when I saw they
have exactly the get key-value pair function I talked about. See

http://msdn.microsoft.com/en-us/library/system.exception.data(v=VS.80).aspx
http://msdn.microsoft.com/en-us/library/5whzhsd2(v=VS.80).aspx

That must be used for logging purposes only, right? I can't imagine it
should be used by a handler.