> From: Corey Jewett [mailto:[EMAIL PROTECTED]] > > A question on the strategy of creating exceptions to just > float around. > > It's my understanding that throwing exceptions causes a lot > of work in the JVM. What I'm unclear on is if this work is > from the throw, or from the Exception instantiation. If it's > from the instantiation then it would probably be a good idea > to bury this strategy under a debugging flag. Can anybody > clear this up for me?
Creating is just creating. The issue is in the throwing. The exception needs to fill in the stack trace, and go back through the stack trace in reverse order until it is finally handled. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
