|
|
@@ -50,6 +50,17 @@ Aer has builtin native support for UTF-8 characters. That is, you are not restri
|
|
50
|
50
|
or methods. Any UTF-8 encoded natural language can be used without the need for ICU or any other internationalization package.
|
|
51
|
51
|
|
|
52
|
52
|
|
|
|
53
|
+## Hand-Coded Project
|
|
|
54
|
+The reason why performance rocks under AerScript and its PH7 Engine relies in the fact that is a hand-coded project. That is,
|
|
|
55
|
+Aer does not use any external tools to generate it's lexical analyzer such as lex or flex, nor does not use LALR(1) parsers such
|
|
|
56
|
+as Bison or YACC to generate it's parser. By acting so, the lexer and the parser are thread-safe, full re-entrant, generate
|
|
|
57
|
+better error message, takes less space in the source tree and are easier to maintain.
|
|
|
58
|
+
|
|
|
59
|
+Aer is written in C. It compiles and runs unmodified on any platform including restricted embedded device with a C compiler.
|
|
|
60
|
+The PH7 Engine have been extensively tested under Windows and UNIX including Linux and FreeBSD. If you have successfully compiled
|
|
|
61
|
+and tested Aer in an exotic environment or a proprietary UNIX, please let us know.
|
|
|
62
|
+
|
|
|
63
|
+
|
|
53
|
64
|
## Build Instructions
|
|
54
|
65
|
Aer is a multi-platform software, that can be built on any Operating System. On Unix-like. macOS and Cygwin it is as
|
|
55
|
66
|
easy as to fetch the source code and issue single command:
|
