From erixtekila at gmail.com  Sat May 20 12:32:24 2006
From: erixtekila at gmail.com (erixtekila)
Date: Sat May 20 12:33:45 2006
Subject: [as2api-dev] Will as2api support other ECMA-like language ?
Message-ID: <83d0ca08d5ba3892e7644367e5bca076@gmail.com>

Hi,


I was wondering of the difficulty of implementaing haXe, as3 and mxml.
Let me know.

-----------
erixtekila
http://blog.v-i-a.net/


From dave at badgers-in-foil.co.uk  Sat May 20 22:18:05 2006
From: dave at badgers-in-foil.co.uk (David Holroyd)
Date: Sat May 20 22:18:11 2006
Subject: [as2api-dev] Will as2api support other ECMA-like language ?
In-Reply-To: <83d0ca08d5ba3892e7644367e5bca076@gmail.com>
References: <83d0ca08d5ba3892e7644367e5bca076@gmail.com>
Message-ID: <20060520221805.GA14930@badgers-in-foil.co.uk>

On Sat, May 20, 2006 at 02:32:24PM +0200, erixtekila wrote:
> I was wondering of the difficulty of implementaing haXe, as3 and mxml.
> Let me know.

Hmm, I'm not sure...


For haXe, isn't there already a plan in place for API doc extraction?  I
see this post by Nicolas,

  http://lists.motion-twin.com/pipermail/haxe/2005-December/001074.html


As far as MXML is concerned, no one where I work is currently using it,
so I don't know much more about it than can be discovered by a quick bit
of Googling.  It *looks* like a reference-generating tool for MXML would
need to be significantly different to as2api as currently implemented
(i.e. it would not only have to cope with very different input data, but
would need to document things like GUI widgets, instead of 'classes', I
assume).  Are my assumptions correct?


Then for AS3, I'm not yet sure what all the syntactic differences from
AS2 are, but I plan to incoporate support for AS3 into as2api at some
point.  I know that the current as2 parser in as2api will choke on the
as3 XML-literal and regular-expression-literal syntax features, at
least.  Does anyone have a large set of example as3 code that I could
look at?


dave

-- 
http://david.holroyd.me.uk/