Prev | Current Page 785 | Next

L. McColl-Sylvester and F. Ponticelli

"Professional haXe and Neko"

This is a notable feature because the programmer does not have to worry too
much about maintaining short code and even more, he will not have to worry on how the JavaScript
code has to be partitioned in files to include only when they are really necessary. The compiler produces
just one file with just the needed code and no more.
The haXe - produced JavaScript plays nicely with other libraries. It does not change the native objects
(the only exceptions are a couple of methods added to the Array type and the notation used to mark a type
as a class) and, thus, does not conflict with third - party libraries. Using the extern keyword, an example
is provided in Chapter 6 in the ??? JavaScript External Libraries ??? section. You can even use third - party
libraries in your haXe code with a minimum effort.
The class and package system of haXe is very well integrated in JavaScript; both features are not
available in current implementations of the most diffused browsers.
The JavaScript output is well - written and easy - to - read code; you can confidently build a library in
haXe and distribute it to pure JavaScript developers without the fear that the code is hard to understand
or debug.


Pages:
773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797