[Laszlo-dev] For Review: Change 20090415-ptw-w Summary: Improve catch-errors and backtrace efficiency

[André Bargull]

On 4/17/2009 3:15 PM, P T Withington wrote:
> On 2009-04-16, at 18:31EDT, André Bargull wrote:
> 
>>> +      // Not sure why we turn this off now...
>>>       options.putBoolean(Compiler.CATCH_FUNCTION_EXCEPTIONS, false);
>>
>> I think it's turned off, so you won't emit more try..catch blocks when 
>> you descend into children.
> 
> Not sure if that is the right thing.  If there are children that are 
> upward closures, you probably want them to have their own try/catch.

I don't know for sure, you (pl.) are the compiler wizards! ;-)

> 
>> A try..catch block is created in this case, but I don't think that's 
>> right here:
>> ---
>> <method name="blubb_5" returns="void" >
>>  this.a;
>> </method>
>> ---
> 
> Yeah, I thought about that.  In theory, I think `this` could be null if 
> you were to force it using Function/call or Function/apply (at least in 
> DHTML),
> but maybe we should assume that is so rare it is not worth the overhead 
> of try/catch?

Shouldn't it be the global object [1] instead of `null` in that case?


[1] or the "magic package-global" object in AS3