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 gosmith@adobe.com designates
 64.18.1.77 as permitted sender)
From: Gordon Smith <gosmith@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Sun, 18 Nov 2012 16:32:45 -0800
Subject: RE: Flex 5 in haxe
Thread-Topic: Flex 5 in haxe
Thread-Index: Ac3EIDZOYfuxpjvIR3ynUmF2T4YJZgBzHbEg
Message-ID: 
 <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>
In-Reply-To: 
 <CALorpXcp-EMNpHa4pyfhytZsCoK-C2y2fQi4d4PV_U+69bQPXw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> 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 ht=
tp://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 =3D Std.parseFloat(neko.Sys.stdin().readLine());

neko.Lib.println("How Many Iterations?");
var count : Int =3D Std.parseInt(neko.Sys.stdin().readLine());

// Initialization of variables
var f0 : Float;
var df0 : Float;
var p0 : Float;
var p1 : Float;

p0=3Dx0; // Initial guess at x0

for(i in 0...count)=20

{

f0=3Dx0*x0-401; // f(x) =3D x^2-401 or evaluate sqrt(401)
df0=3D2*x0;     // f'(x) =3D 2x (derivative of f(x))

p1=3Dp0-(f0/df0);  // p1=3Dp0-(f(x)/f'(x)) Newton's Method Here

neko.Lib.println("p1 =3D " + p1);
p0=3Dp1; //switch variables for next iteration
x0=3Dp1; //switch variables for next iteration

}
}
}ess at x0

for(i in 0...count)=20

{

f0=3Dx0*x0-401; // f(x) =3D x^2-401 or evaluate sqrt(401)
df0=3D2*x0;     // f'(x) =3D 2x (derivative of f(x))

p1=3Dp0-(f0/df0);  // p1=3Dp0-(f(x)/f'(x)) Newton's Method Here

neko.Lib.println("p1 =3D " + p1);
p0=3Dp1; //switch variables for next iteration
x0=3Dp1; //switch variables for next iteration

}
}
}

-----Original Message-----
From: Nicholas Kwiatkowski [mailto:nicholas@spoon.as]=20
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>wr=
ote:

>
> I only know a little about Haxe. Could you comment on what would be=20
> required (in terms of skills and effort) to port Flex to Haxe? I know=20
> it's ActionScript like but is missing a few features that Flex may be usi=
ng?
> Other than compiling to multiple targets does it have any other=20
> significant advantages? Any idea if there are likely to be major=20
> performance issues due to the fact that Flex is reasonably complex and de=
signed 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 an=
d use.

Haxe is unique in that that single C++ like language then can output to nav=
tive apps, SWF, Silverlight, HTML/JS, etc.  It's not very good at any of th=
em, and the biggest problem with the language is that it limits itself to t=
he least common detonator of all the platforms it supports.


> Currently I see no compelling reason to move to the new VM when it=20
> comes out. Once we know more about it that may change but it sounds=20
> like it wont be compatible with AS3. The existing one for the moment=20
> works and is likely to be around for many many years.
>
>
AS2 is still well supported (and, surprisingly used) in most outputs.  No r=
eason 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.