incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niel Drummond <niel.drumm...@grumpytoad.org>
Subject Re: [RT] haxe reality check
Date Thu, 23 Feb 2012 13:06:28 GMT
Just wanted to drop a small note.

If it is decided to prototype something in haxe, or check whether a
required feature can be implemented with macros, I'm happy to provide
help coding, advise or fetching the right person from the haxe
community.

All the best,

- Niel

On 23/02/2012, Martin Heidegger <mh@leichtgewicht.at> wrote:
> On 23/02/2012 17:53, Left Right wrote:
>> There is a confusion about the way in which E4X will not be accessible -
>
> e4x is a language feature. Different access is per-definition not e4x.
> It just means we would
> need to use other tools.
>
>> inline function getDefinition(name) { return untyped
>> __global__["flash.utils.getDefinitionByName"](name); }
>
> Yes, it would be possible to use the functions but it would not be
> possible to provide
> functions or constants that Flex users could refer to.
>
>> However, GPL vs Apache license seems like a tough one...
>
> As long as the things in haXe are not required to be checked in it would
> be good enough.
>
> yours
> Martin.
>

-- 
Sent from my mobile device

Mime
View raw message