incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roland Zwaga <rol...@stackandheap.com>
Subject Re: Does Falcon need to take CDATA sections into account when parsing <fx:string/>?
Date Tue, 30 Oct 2012 20:21:36 GMT
good point ;)

On 30 October 2012 21:13, Gordon Smith <gosmith@adobe.com> wrote:

> The switch should eventually be a new language namespace specifying a new,
> improved version of MXML such as xmlns:fx="http://ns.adobe.com/mxml/2013"
> for MXML 2013.
>
> - Gordon
>
> -----Original Message-----
> From: Roland Zwaga [mailto:roland@stackandheap.com]
> Sent: Tuesday, October 30, 2012 3:19 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Does Falcon need to take CDATA sections into account when
> parsing <fx:string/>?
>
> Yea, I guess in this case back-ward compatibility beats purely correct
> behaviour. The very best option would probably be a -compatibility switch,
> but that might complicate things more?
> If this is the only case where we run into a scenario like this, that
> might be overkill. But perhaps if we stumble upon more cases we could
> consider such a switch?
>
> Roland
>
>
> > In my opinion, this behavior of the old compiler is inconsistent and
> > should be considered a bug. So we have to decide how bug-compatible we
> > want Falcon to be with the old compiler. It may be difficult to even
> > achieve bug-compatibility in cases like this.
> >
> > Could we live with Falcon compiling it as a string with one space,
> > regardless of whether there is CDATA or not?
> >
>



-- 
regards,
Roland

-- 
Roland Zwaga
Senior Consultant | Stack & Heap BVBA

+32 (0)486 16 12 62 | roland@stackandheap.com | http://www.stackandheap.com

http://zwaga.blogspot.com
http://www.springactionscript.org
http://www.as3commons.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message