On Thursday, Mar 20, 2003, at 11:33 America/Denver, Brian Gray wrote:
On Wednesday, March 19, 2003, at 04:50 PM, Greg Colvin wrote:
Without runtime library support it will be difficult to do, but not
impossible --
the Oracle runtime has platform-specific code for capturing the stack
trace on all
On Wednesday, March 19, 2003, at 04:50 PM, Greg Colvin wrote:
Without runtime library support it will be difficult to do, but not
impossible --
the Oracle runtime has platform-specific code for capturing the stack
trace on all
the of the many platforms we support. I can't post the code, but
cou
std::exception once had a where() member for this purpose, but it
didn't survive.
Without runtime library support it will be difficult to do, but not
impossible --
the Oracle runtime has platform-specific code for capturing the stack
trace on all
the of the many platforms we support. I can't p
I would love boost to provide an exception class/framework/something
with this capability to encourage collection of context information,
which would make problem diagnosis so much easier.
Perhaps I could relate some of my experience and put some ideas up
for discussion?
I'm interested (in fact I n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trevor Taylor wrote:
|
| Perhaps I could relate some of my experience and put some ideas up
| for discussion?
I would be interested.
Thomas
- --
Dipl.-Ing. Thomas Witt
Institut fuer Verkehrswesen, Eisenbahnbau und -betrieb, Universitaet
Hannover
voi
As a software user I am frequently frustrated by "an error occurred"
like failure messages. As a developer I know that the software *knows*
exactly what failed, why, and exactly what it was doing at the time, but
doesn't pass any of this information on.
Recently I developed some C++ where for the f
