You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@royale.apache.org by GitBox <gi...@apache.org> on 2018/05/23 21:16:12 UTC

[GitHub] aharui commented on issue #246: Issues when porting Starling

aharui commented on issue #246: Issues when porting Starling
URL: https://github.com/apache/royale-asjs/issues/246#issuecomment-391499106
 
 
   Is there any way you can make individual GitHub Issues for these items and include one- or two-file test cases?  It will be easier to discuss them individually.
   
   The first 3 (Error, namespace, import) I could swear we have similar code compiling just fine so we'll have to try it again with a more watchful eye.
   
   ||= I have not tried so sure, could be a bug there.
   
   There is an E4X implementation for Royale, so you should be able to do most E4X without modifying your code.  You will need the XML.swc.  If it has too many dependencies on other SWCs we can look into breaking those dependencies.
   
   I'm trying to see what Google Closure needs to allow subclassing an Extern as part of Issue #234.
   
   Regarding super(), do you mean that members variables were not initialized or that the APIs simply didn't exist?  If you want ES6 super(), someone will need to create an ES6 emitter.  Right now, we output ES5 and super() is transpiled into Google Closure "base" calls.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services