Are you changing the compiler? I thought you could just add:
function debugger{};
to missing.js so it results in:
public class debugger {};
and
package flash.debugger {
native function enterDebugger():void;
}
to one of our swcs? Although I have to say I'm a bit uncomfortable about
adding undocumented Flash APIs to our code base. We are not supposed to
use APIs that are "reverse-engineered". Do we have proof that Adobe
documented it at one point in time?
HTH,
-Alex
On 7/18/17, 5:05 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote:
>I'm working on adding support for the debugger statement to the compiler
>(FLEX-35343). I can successfully emit the debugger statement in the
>generated JS so far.
>
>I'm not yet sure if I can make it work on the SWF side. I figured out
>where
>I can generate bytecode instructions in ABCGeneratingReducer. If I can
>figure out how to generate bytecode to call enterDebugger() (or whatever
>the function is called), the debugger statement will work in both SWF and
>JS.
>
>- Josh
>
>On Sun, Jul 16, 2017 at 9:22 AM, Josh Tynjala <joshtynj...@gmail.com>
>wrote:
>
>> If it were a variable or function, it could be defined somewhere like
>> that. It's a statement, though, so it needs to be added to where Falcon
>> creates the AST from the ActionScript code. Then, it also needs to emit
>>the
>> statement as JS in FalconJX. On the SWF side, it should be translated to
>> appropriate bytecode to call enterDebugger().
>>
>> - Josh
>>
>> On Jul 16, 2017 8:56 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>>
>>> What needs to be modified? Does it need to be added to NativeJSType
>>> enums? Somewhere else?
>>>
>>> I’m really not clear on when things to be added to that and when they
>>> need to be in typedefs.
>>>
>>> > On Jul 16, 2017, at 6:51 PM, Harbs <harbs.li...@gmail.com> wrote:
>>> >
>>> >> The compiler needs to be modified to support the debugger statement.
>>>
>>>
