Andrew Haley wrote:
Indeed.  The problem is that anything you do when catching an
OutOfMemoryException risks running out of memory!  There's not much
any java program can do other than logging the failure and exiting.

To be pedantic, it's OutOfMemoryError, and the same applies largely to any other Error (except possibly in the case of reflection tools).
--
Chris Burdess




_______________________________________________
Classpath mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/classpath

Reply via email to