C++ and Java EGMLs have a few (not many) differences. It is important to know how to deal with those differences.
The arrival of G-C++ as a conversion tool should make a Java EGML to C++ EGML conversion much easier.
| G-java | G-C++ |
|---|---|
| import | using |
In G-java, packages are all in org.gjava.runner.Functions. Inside functions, they are ordered. See G-java's API for more detailed information.
In G-C++, functions are ordered by GML and EGML (for EGML-exclusive). This separation will soon be dropped for a more similar packaging.
In G-java, a class is defined by class name{ something }, in G-C++, you need to add ; to the end of the class.
| G-java | G-C++ |
|---|---|
| extends | : |
Some functions are available in G-C++ and not in G-java, and some functions are available in G-java and not in G-C++. Usually, functions in G-C++ but not in G-java are from recent EGML versions while functions in G-java not in G-C++ come from GML.
G-java requires Equals in string comparison, while G-C++ requires == and does not have the Equals method.