Re: Re: Detecting finally blocks?

Ok - but does this address Jonathan's problem? I'd assume he's interested in
whenever the finally { } code is executed, not just in an exception handler
(that is, also when it's executed during a regular return.) He could
identify the code in the catch-all handler, then search for it elsewhere -
but it may not look exactly the same. Perhaps I misunderstood his question.

 - Godmar

On Thu, Dec 17, 2009 at 9:20 PM, Scott Vachalek <[email protected]> wrote:

> True... I always think of those as finally blocks, but I guess technically
> they are not.  If you want to ignore them they should be pretty easy to
> identify.
>
>
> On Thu, Dec 17, 2009 at 6:14 PM, Godmar Back <[email protected]> wrote:
>
>> On Thu, Dec 17, 2009 at 8:35 PM, Scott Vachalek <[email protected]>wrote:
>>
>>> it's not something you can rely upon entirely.  But I've never seen a
>>> null catch generated by javac for any other reason.  The contents of the
>>> handler (save exception, repeat finally code, throw saved exception) are
>>> also very predictable.
>>
>>
>> It's also used for synchronized (obj) { } blocks where a monitorexit is
>> required.
>>
>>  - Godmar
>>
>>
>>
>

-- 
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws