Jacob Carlborg d...@me.com wrote in message
news:j2qn7n$1db7$1...@digitalmars.com...
On 2011-08-21 02:26, Jonathan M Davis wrote:
The short answer: You don't. It's an incredibly bad idea.
The long answer: You catch Error - or OutOfMemoryError if you want that
specific one. So, you could try
On Thursday, August 25, 2011 11:38 Nick Sabalausky wrote:
Jacob Carlborg d...@me.com wrote in message
news:j2qn7n$1db7$1...@digitalmars.com...
On 2011-08-21 02:26, Jonathan M Davis wrote:
The short answer: You don't. It's an incredibly bad idea.
The long answer: You catch Error - or
On 2011-08-21 02:26, Jonathan M Davis wrote:
On Saturday, August 20, 2011 18:18:25 Sean Eskapp wrote:
bearophile:
As far as I know they have decided to make memory overflow errors, so
they are
not exceptions, you can't catch them. Other people will confirm this or not.
In this case, how
Sean Eskapp:
Does nothrow mean the function itself does not through exceptions, or that the
function body, as well as any called functions, do not throw? I wonder because
allocating new memory inside a @safe nothrow function works, even though I'm
used to new allocations throwing exceptions
On 08/20/2011 08:18 PM, Sean Eskapp wrote:
bearophile:
As far as I know they have decided to make memory overflow errors, so they are
not exceptions, you can't catch them. Other people will confirm this or not.
In this case, how would you go about handling out-of-memory situations? A
systems
== Quote from Timon Gehr (timon.g...@gmx.ch)'s article
On 08/20/2011 08:18 PM, Sean Eskapp wrote:
bearophile:
As far as I know they have decided to make memory overflow errors, so they
are
not exceptions, you can't catch them. Other people will confirm this or not.
In this case, how
On Saturday, August 20, 2011 18:18:25 Sean Eskapp wrote:
bearophile:
As far as I know they have decided to make memory overflow errors, so
they are
not exceptions, you can't catch them. Other people will confirm this or not.
In this case, how would you go about handling out-of-memory
On Saturday, August 20, 2011 16:41:01 Sean Eskapp wrote:
Does nothrow mean the function itself does not through exceptions, or that
the function body, as well as any called functions, do not throw? I wonder
because allocating new memory inside a @safe nothrow function works, even
though I'm
