Is this only for binding to consts and literals? If so, why do we want to
add syntax instead of having the compiler figure out that the value will
never change? If not, how will you know when to assign the value?
On 4/24/12 7:06 AM, "Roland Zwaga" <rol...@stackandheap.com> wrote:
> Hi there,
>
> I welcome this addition as well! I've had plenty of times when I just
> wanted to assign a value once, without binding, when I still needed the
> curly braces because otherwise the compiler would just see the value as a
> literal.
> From what I can gather, this wouldn't have any bad effects on anything else.
>
> cheerios,
>
> Roland
>
> On 24 April 2012 15:50, Justin Mclean <jus...@classsoftware.com> wrote:
>
>> Hi,
>>
>> I think this is a nice idea. As this involves an addition to MXML syntax
>> (ie attr="${value}" rather than attr="{value}" to bind to value once) does
>> anyone have any suggestions on how we can take this forward?
>>
>> Are there any disadvantages/issues that if this was applied that I'm not
>> seeing?
>>
>> Thanks,
>> Justin
>
>
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
