Cool. Thanks.
> On Mar 9, 2017, at 9:06 AM, Alex Harui <aha...@adobe.com> wrote:
>
> OK, pushed a fix for this. IMO, it was a too-sensitive check in Falcon.
> It is allowed in SWF.
>
> -Alex
>
> On 3/8/17, 3:18 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>
>> FWIW, I’m using FDT, and it does not report an error with the interfaces.
>> (It’s only reported when I actually compile it.) I don’t know if that’s
>> an indication that it’s okay with Flash, but I’d guess that yes.
>>
>>> On Mar 9, 2017, at 1:10 AM, Alex Harui <aha...@adobe.com> wrote:
>>>
>>>
>>>
>>> On 3/8/17, 11:29 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>>>
>>>> In my quest to remove circular dependencies, I’ve created a whole slew
>>>> of
>>>> interfaces and I’ve come across an interesting problem:
>>>>
>>>> This works correctly when dealing with concrete classes. For some
>>>> reason
>>>> when done with interfaces, I get the error above.
>>>>
>>>> Is this an easy fix?
>>>
>>> Hard to say. One good test would be to see if this works with the
>>> regular
>>> Flex SDK MXMLC. There's also a question about whether the runtime
>>> allows
>>> this or not. I don't see why it shouldn't work. If it is just that
>>> Falcon is too picky, that should be "easy".
>>>
>>> -Alex
>>>
>>
>
