> 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*x0401; // f(x) = x^2401 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*x0401; // f(x) = x^2401 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: flexdev@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 rewrite 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.
