flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-35069) .. notation failing in XML
Date Mon, 11 Apr 2016 15:35:25 GMT

    [ https://issues.apache.org/jira/browse/FLEX-35069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235306#comment-15235306
] 

Harbs commented on FLEX-35069:
------------------------------

The spec clearly states that namespaces do not need prefixes. In fact, if there's a default
namespace, it's probably not prefixed. It stands to reason that there needs to be a way to
specify a non-prefixed namespace in E4X statements. I probably found this syntax by trial
and error.

I'm fine with considering this a low-priority bug until someone complains. I've never had
a need for this in real-life situations.

> .. notation failing in XML
> --------------------------
>
>                 Key: FLEX-35069
>                 URL: https://issues.apache.org/jira/browse/FLEX-35069
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: FalconJX
>    Affects Versions: Apache FalconJX 0.6.0
>            Reporter: Harbs
>
> The following code fails:
> var catalog_item = xml..('http://ns.adobe.com/mxml/2009')::catalog_item[0];
> The compiler gives the following message:
> [mxmlc] Error: '..' is not allowed here
> This should be valid E4X. I'm not sure what it is about this expression which is failing.
The following does seem to be accepted:
> var script:XML = xml..script[0].children()[0];



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message