It was.
Down to 10 GCC errors when cross-compiling the SDK with FalconJX ;-)
EdB
On Fri, Oct 10, 2014 at 7:42 PM, Alex Harui wrote:
> Sounds right to me.
>
> On 10/10/14, 10:33 AM, "Erik de Bruin" wrote:
>
> >Yeah, I know it “lands” there … Got it: the compiler actually marks the
> >object
Sounds right to me.
On 10/10/14, 10:33 AM, "Erik de Bruin" wrote:
>Yeah, I know it “lands” there … Got it: the compiler actually marks the
>object literal prop as ‘NonResolvingIdentifierNode’, which is currently no
>special cased, so FalconJX treats it as an accessor node: guess I’m going
>to ma
Yeah, I know it “lands” there … Got it: the compiler actually marks the
object literal prop as ‘NonResolvingIdentifierNode’, which is currently no
special cased, so FalconJX treats it as an accessor node: guess I’m going
to make ‘emitIdentifier' a bit more complex ;-)
EdB
On Fri, Oct 10, 2014 a
Did you look at emitIdentifier in JSFlexJSEmitter.java? I would expect it
would all come down to the logic in there.
On 10/10/14, 8:50 AM, "Erik de Bruin" wrote:
>Hi,
>
>I have:
>
>
>public class MyClass
>{
>private var myObject:Object = { visible: true };
>
>private var _visible:Boolean;
> pub
Hi,
I have:
public class MyClass
{
private var myObject:Object = { visible: true };
private var _visible:Boolean;
public function get visible():Boolean
{
return _visible;
}
public function set visible(value:Boolean):void
{
_visible = value;
}
}
When I feed this to Falcon/FalconJX (with Flex
