Subject: Re: Allocating on the stack and *only* on the stack From: Erik Naggum <erik@naggum.net> Date: 12 Dec 2000 20:43:16 +0000 Newsgroups: comp.lang.lisp Message-ID: <3185642596488733@naggum.net> * Knut Arild Erstad | Actually, this _shouldn't_ be a problem for Java programmers; there | are no destructors in Java. Unfortunately, a lot of Java programmers | (even book authors) seem to be using finalizers as destructors. You're right! I had actually missed that, and have been thinking in destructor terms myself. Thanks! Goes to show how little I use them. | Java also has a try/finally clause that works like unwind-protect, but | of course, you can't use macros to hide the details. I think the ugliness of such verbose forms deters people from doing the right thing. Proper handling of exceptional situtations in Java is also too verbose for my comfort. Maybe I'm just spoiled. #:Erik -- "When you are having a bad day and it seems like everybody is trying to piss you off, remember that it takes 42 muscles to produce a frown, but only 4 muscles to work the trigger of a good sniper rifle." -- Unknown