[phobos] Calling abort() on unhandled exception

[Leandro Lucarella]

Andrei Alexandrescu, el 29 de julio a las 21:37 me escribiste:
> Sean Kelly wrote:
> >On Jul 29, 2010, at 8:21 PM, Walter Bright wrote:
> >>Andrei Alexandrescu wrote:
> >>>Walter Bright wrote:
> >>>>I think we misunderstand each other. A file copy program that fails due to, say, the disk being full, should not produce a core dump. It should produce an error message like:
> >>>>
> >>>> error: disk full
> >>>>
> >>>>An uncaught exception is NOT an invalid or crashed program in D.
> >>>I think Sean talks about Throwable objects that are not Exception objects.
> >>>
> >>It's reasonable for seg fault exceptions to produce a core dump. It isn't for recoverable Exceptions, or for non-recoverable ones like out of memory.
> >
> >At the moment, we don't differentiate between seg faults and non-recoverable errors.  Though seg faults are only thrown as exceptions on Windows which doesn't have core dumps anyway, as far as I know. For what it's worth, I was investigating this bug:
> >
> >http://d.puremagic.com/issues/show_bug.cgi?id=4385
> 
> I see. Overall, my opinion is that regular exceptions that escape
> main(0 should simply print their error message to stderr and
> exit(1). There should be no stack trace, abort(), core dump, or
> anything worse than that. Print the string and exit(1). Anything
> more will force most people to actually insert a try/catch in main
> to do the simple thing.

Calling abort() on Linux will simply print "Aborted". Do you think is
that bad that worth being completely different than any other PL and
making debug an uncaught exception almost imposible???

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Hey you, don't tell me there's no hope at all
Together we stand, divided we fall.