At 9:28 PM +0300 4/10/09, Stoyan Damov wrote: >if acquireResource could throw an error, the correct way to handle it >is in an outer try block: > >as opposed to this anti-pattern (again widely used): >
Hi Stoyan: What is your reasoning here? Why would it be preferred to make the runtime setup two exception frames? That has to be more expensive than a simple test against null? I mean, I see there is some exception type safety in the two frame approach, but is there some horrible hole in the single frame method? or is two frames just "taste" ? -- Ward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
