The reason for this choice is that, although standard languages are more easily read by
people, XML trees are far easier for machines to generate and navigate. NXML also provides a more
simple way to include file and line information for the compiled .hx files so that more accurate
debugging information can be provided to the developer. By adopting NXML, any language that
supports XML is able to build scripts that can then be compiled by the Neko compiler for execution
by vthe virtual machine.
NekoML, on the other hand, is a different kettle of fish as it is styled around functional languages from
the ML family, with a specific similarity to Objective Caml. ML languages provide a very organic method
of processing data using nested functions and recursion that reduces the amount of used resources and is
very well suited to symbolic processing and pattern matching as used by compilers. This makes
NekoML the perfect language for creating your own compilers.
Although the Neko compiler was originally written in Objective Caml, it is now written in NekoML
and compiled by the Neko compiler.
Pages:
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55