This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: V3 PATCH to __verbose_terminate_handler
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Theodore Papadopoulo <Theodore dot Papadopoulo at sophia dot inria dot fr>
- Cc: Phil Edwards <phil at jaj dot com>, Jason Merrill <jason at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: 19 Dec 2002 18:00:31 +0100
- Subject: Re: V3 PATCH to __verbose_terminate_handler
- Organization: Integrable Solutions
- References: <200212191647.gBJGlNPD014930@mururoa.inria.fr>
Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr> writes:
| gdr@integrable-solutions.net said:
| > What should happen? Should we nevertheless be verbose about program
| > termination? What if in step 2c) Programmer specified -ansi?
| > Put differently, should -ansi also be a "link-time" switch?
|
| I may be wrong but the choice of the default terminate handler is
| only a link time flag. It should boil down to linking with one object
| with default behavior or another one with the non-ansi version.
In that case I would rather see a switch distinct from -ansi.
-ansi is too bloated, IMHO.
| I have been surprised by this abort too often for not considering
| this as a useful extension.
Hmmm, do you mean that a dry "zsh: ./a.out: abort" is clearer and more
useful that a message saying that the program was terminated because
of an uncaught exception?
-- Gaby