[Issue 8135] throwing Error runs finally handler

d-bugmail at puremagic.com d-bugmail at puremagic.com
Thu May 24 09:42:54 PDT 2012


http://d.puremagic.com/issues/show_bug.cgi?id=8135



--- Comment #10 from Alex Rønne Petersen <alex at lycus.org> 2012-05-24 18:44:33 CEST ---
(In reply to comment #8)
> (In reply to comment #4)
> > FWIW, I'm all for making Errors actually fatal and terminating the runtime
> > immediately, but then OutOfMemory*Error* HAS GOT TO GO.
> 
> Then you could mark almost nothing as nothrow.

True.

> 
> I think OutOfMemory should be an error.  If you want to override the behavior
> because you have special circumstances, that should be possible (i.e. somehow
> prevent out of memory error from being thrown, but instead handle the situation
> in a different way).
> 
> What about an enhancement of adding GC.mallocNoError and friends which instead
> return null when a memory block is not available instead of throwing?

That could work too. I really just want the GC to not assume that an allocation
error is fatal.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list