; >>> should probably have a different JBurg pattern and reduce method just
> >>>for
> >>> this case.
> >>>
> >>> I'm also not convinced this covers all the relevant situations where a
> >>> coerce_a might be necessary. For example
t situations where a
>>> coerce_a might be necessary. For example, suppose that instead of being
>>> assigned to a left-hand-side of type *, the ternary expression is being
>>> passed as a argument to a function that has a type * parameter. That
>>> might also need
o a left-hand-side of type *, the ternary expression is being
>> passed as a argument to a function that has a type * parameter. That
>> might also need a coerce_a.
>>
>> I'd put a comment in the code that this is questionable. But if it gets
>> your app further towards worki
. That
>might also need a coerce_a.
>
>I'd put a comment in the code that this is questionable. But if it gets
>your app further towards working, it's good.
>
>- Gordon
>
>-Original Message-
>From: Alex Harui [mailto:aha...@adobe.com]
>Sent: Wednesda
lto:aha...@adobe.com]
Sent: Wednesday, October 02, 2013 11:52 AM
To: dev@flex.apache.org
Subject: Re: [FALCON] using coerce_a
The code only thinks about coercing if there is a bracket [] node. It gets the
type of the left hand side via resolveType and compares the resolveType of the
clause node an
setproperty
>>> private,flash.events:EventDispatcher,Object,private,,http://adobe.com/A
>>>S
>>>3
>>>/
>>>2006/builtin:null
>>>
>>>I'm beginning to think this is an AIR bug since the Falcon ABC runs fine
>>>on Flash.
.
>>
>>
>>Thanks,
>>-Alex
>>
>>
>>
>>On 9/30/13 10:50 PM, "Alex Harui" wrote:
>>
>>>There's no error, the Dictionary value appears be a Number instead of an
>>>instance.
>>>
>>>Are you sure
nstance.
>>
>>Are you sure that Vector access doesn't come through this code? I think
>>I'll start by testing only for ANY_TYPE and adding a coerce_a instead of
>>calling coerce() which would also coerce to any destination type.
>>
>>Thanks for the advice,
__
>From: Darrell Loverin [darrell.love...@gmail.com]
>Sent: Monday, September 30, 2013 6:11 PM
>To: dev@flex.apache.org
>Subject: Re: [FALCON] using coerce_a
>
>I generally agree. I don't think I'd try to do anything inside the ternary
>exp
estination type.
Thanks for the advice,
-Alex
From: Darrell Loverin [darrell.love...@gmail.com]
Sent: Monday, September 30, 2013 6:11 PM
To: dev@flex.apache.org
Subject: Re: [FALCON] using coerce_a
I generally agree. I don't think I'd try to do an
type (not just
> Dictionary), is type *. So I think it is OK to codegen coerce_a before
> assignment to any foo[bar] expression.
>
> Darrell, do you agree or disagree?
>
> - Gordon
>
>
> -Original Message-
> From: Darrell Loverin [mailto:darrell.love...@gmail.co
ell, do you agree or disagree?
- Gordon
-Original Message-
From: Darrell Loverin [mailto:darrell.love...@gmail.com]
Sent: Monday, September 30, 2013 3:41 PM
To: dev@flex.apache.org
Subject: Re: [FALCON] using coerce_a
coerce_a Operation
Coerce a value to the any type.
Format
coerce_a
Form
remind me what the "a" in coerce_a means?
>
> - Gordon
>
> -Original Message-
> From: Alex Harui [mailto:aha...@adobe.com]
> Sent: Monday, September 30, 2013 2:43 PM
> To: dev@flex.apache.org
> Subject: [FALCON] using coerce_a
>
> Gordon, Darrell (
Can you remind me what the "a" in coerce_a means?
- Gordon
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Monday, September 30, 2013 2:43 PM
To: dev@flex.apache.org
Subject: [FALCON] using coerce_a
Gordon, Darrell (mostly)
My latest problem appear
Gordon, Darrell (mostly)
My latest problem appears to be in assigning to a Dictionary. For the
following code:
var dict:Dictionary = new Dictionary();
Var i:int;
Dict["foo"] = (i == 0 ? new SomeClass() : new SomeOtherClass());
MXMLC generates a coerce_a after the constructProp for both SomeClas
15 matches
Mail list logo
