Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of mahnmal@gmail.com designates
 209.85.220.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <149F8129B58B2D418508E63117D9C5419B5B360077@nambx05.corp.adobe.com>
References: 
 <CAMFKFRjVqyYP6+NV+-nw_YDc_UNTDeWnUg-AYZvnkhk4o7Q7uw@mail.gmail.com>
 <813661353067194@web29g.yandex.ru>
 <CAGw=_tzy_BGV9vFZNFR0x04t7yeQkReVSE1RHM5BYEM4KwctfQ@mail.gmail.com>
 <CADPmPauMdRSGO7BQaHfC_w4q=wO4kyk_HT42XoM+g66rR_8zrA@mail.gmail.com>
 <2AF11B3E-2586-4973-9030-A225C35F0879@classsoftware.com>
 <CALorpXcp-EMNpHa4pyfhytZsCoK-C2y2fQi4d4PV_U+69bQPXw@mail.gmail.com>
 <149F8129B58B2D418508E63117D9C5419B5B360077@nambx05.corp.adobe.com>
From: John Cunliffe <mahnmal@gmail.com>
Date: Mon, 19 Nov 2012 11:09:43 +0100
Message-ID: 
 <CAE56n039-yzCP_RJJDL-fvU6b26fufZ+FwFtUeeetRq_7u_BDA@mail.gmail.com>
Subject: Re: Flex 5 in haxe
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b33da183122f104ced652bf

--047d7b33da183122f104ced652bf
Content-Type: text/plain; charset=ISO-8859-1

According to Wikipedia: Haxe also includes platform-specific API, but as of
2012, it only supports a subset of the functionality available in each
platform[5] <http://en.wikipedia.org/wiki/Haxe#cite_note-hapi-5>, with only
the Flash platform API fully usable.

On Mon, Nov 19, 2012 at 1:32 AM, Gordon Smith <gosmith@adobe.com> wrote:

> > Haxe is a C++ "like" language.  It is not ActionScript, JavaScript, etc.
>
> It looks more like ActionScript than C++ to me. Below is an example from
> http://haxe.org/doc/snip/newtonmethod . Note that variable declarations
> are
>
>     var f0:Float
>
> not
>
>     Float f0;
>
> - Gordon
>
> class Newton{
>
> public static function main(){
>
> neko.Lib.println("Enter Starting Point");
> var x0 : Float = Std.parseFloat(neko.Sys.stdin().readLine());
>
> neko.Lib.println("How Many Iterations?");
> var count : Int = Std.parseInt(neko.Sys.stdin().readLine());
>
> // Initialization of variables
> var f0 : Float;
> var df0 : Float;
> var p0 : Float;
> var p1 : Float;
>
> p0=x0; // Initial guess at x0
>
> for(i in 0...count)
>
> {
>
> f0=x0*x0-401; // f(x) = x^2-401 or evaluate sqrt(401)
> df0=2*x0;     // f'(x) = 2x (derivative of f(x))
>
> p1=p0-(f0/df0);  // p1=p0-(f(x)/f'(x)) Newton's Method Here
>
> neko.Lib.println("p1 = " + p1);
> p0=p1; //switch variables for next iteration
> x0=p1; //switch variables for next iteration
>
> }
> }
> }ess at x0
>
> for(i in 0...count)
>
> {
>
> f0=x0*x0-401; // f(x) = x^2-401 or evaluate sqrt(401)
> df0=2*x0;     // f'(x) = 2x (derivative of f(x))
>
> p1=p0-(f0/df0);  // p1=p0-(f(x)/f'(x)) Newton's Method Here
>
> neko.Lib.println("p1 = " + p1);
> p0=p1; //switch variables for next iteration
> x0=p1; //switch variables for next iteration
>
> }
> }
> }
>
> -----Original Message-----
> From: Nicholas Kwiatkowski [mailto:nicholas@spoon.as]
> Sent: Friday, November 16, 2012 9:31 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Flex 5 in haxe
>
> On Fri, Nov 16, 2012 at 8:17 AM, Justin Mclean <justin@classsoftware.com
> >wrote:
>
> >
> > I only know a little about Haxe. Could you comment on what would be
> > required (in terms of skills and effort) to port Flex to Haxe? I know
> > it's ActionScript like but is missing a few features that Flex may be
> using?
> > Other than compiling to multiple targets does it have any other
> > significant advantages? Any idea if there are likely to be major
> > performance issues due to the fact that Flex is reasonably complex and
> designed for the Flash VM?
> >
>
> Haxe is a C++ "like" language.  It is not ActionScript, JavaScript, etc.
>  It would be a complete re-write of everything we currently already know
> and use.
>
> Haxe is unique in that that single C++ like language then can output to
> navtive apps, SWF, Silverlight, HTML/JS, etc.  It's not very good at any of
> them, and the biggest problem with the language is that it limits itself to
> the least common detonator of all the platforms it supports.
>
>
> > Currently I see no compelling reason to move to the new VM when it
> > comes out. Once we know more about it that may change but it sounds
> > like it wont be compatible with AS3. The existing one for the moment
> > works and is likely to be around for many many years.
> >
> >
> AS2 is still well supported (and, surprisingly used) in most outputs.  No
> reason to move and essentially invalidate all the work done up to this
> point in time.  If we change technologies (HaXe or AS4) we throw out
> EVERYTHING the community has built up to now.  Sure, we will have a shiney
> new product, but nothing will stand on it.
>

--047d7b33da183122f104ced652bf--