ajwfrost commented on issue #219: URL: https://github.com/apache/royale-compiler/issues/219#issuecomment-1324607925
Hi @Harbs - yes, @joshtynjala had thought this would be a good idea too, and Adobe are fine with it. There are some technical things we'd had to do but my hope is that AIR would be able to adopt (or adapt) the Royale compiler i.e. we would have Royale as the primary source code for the compiler that ends up in the AIR SDK. I'm meant to be having a call with one of our lawyers to confirm that (a) we would be able to take the Royale compiler, adapt it slightly and then distribute it with AIR SDK (which I think is fine, reading the licenses) - and (b) whether we can then contribute back our own updates into the Royale compiler (which is where I think I may have to escalate internally to try to get approvals...). There have been loads of interesting suggestions in the thread that you just posted to (thanks for that hint re abstract classes!) so it's then a case of trying to work out which are highest priority and relatively straightforward to do. Some of the "compile-time only" ones are fairly straightforward (e.g. verbatim strings) but some of them are going to need changes also in the runtime. For example we added support in the compiler for operator overloading, but we've not published it yet because it is a bit of a workaround that needs the AIR runtime interpreter and JIT code to be updated in order for it to work. I hadn't even considered how that sort of thing might then need to work from the JS perspective...! thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@royale.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
