Error Parser / News: Recent posts

This is a minor update release (bug fix).

Error Parser is a code generator for error codes, specially useful when your project span multiple languages and you need to keep the error synchronized (across Java, Python, C++, etc.).

This is a minor release.

Support for Java has been added. The code will generate a Java enum class (if this option is turned on in the option file).

This is release candidate 1 of version 1.0 of Error Parser. The code was completely refactored to be modular and easy to change. Additionally, all known issues were resolved.

Error Parser is a small tool for application developers. It simplifies the management of error codes, error messages and documentation for both small and large projects. This is done by creating a master XML file containing all the necessary information on the errors (value, error message and documentation). ... read more

This release adds support for Python. More specifically, the parser is now able to generate code that can be used by Python to access error codes created outside Python (kept in the XML error file of Error Parser)

The generated code is either a C header file for inclusion in extended modules or a pure Python file. In both cases, two dict objects are created to map symbolic error names and error numbers (one of the dict uses the number as the key, the other one uses the name).

This release adds support for C#. More specifically, the parser is now able to generate code that can be used by C# projects to access error codes from unmanaged code.

Code generation for other languages (Java, Python) will be added in the next few months.

This is a maintenance release (the status was also changed from alpha to beta release - the code is stable).

Error Parser: it generates most of the ingredients needed by software projects to manage error codes (header file, documentation and code to retrieve the error messages) using a master XML file.

This is a maintenance release. It fixes two bugs and add the ability to upgrade on Windows.

From a master XML file, the parser is able to generate most of the ingredients needed by software projects to manage error codes (header file, documentation and code to retrieve the error messages).

This is a maintenance release. It fixes two bugs and add the ability to upgrade on Windows.

From a master XML file, the parser is able to generate most of the ingredients needed by software projects to manage error codes (header file, documentation, code to retrieve the error messages).

This release adds support for multiple languages (for error messages and error documentation), proper documentation of the XML DTDs (and more) and packaging (RPM and Inno Setup).

And, just like the previous release, the parser is able to generate the header file for errors with comments for the doxygen program - the parser will also generate the code used to access the error messages.

From a master xml file, the parser will generate all the ingredients needed for software development (header file, documentation, code to retrieve the error messages).

For this release, the parser is able to generate the header file for errors with comments for the doxygen program. The parser will also generate code that can be used to access the error messages.

This release does not include i18n (of messages and documentation), has little packaging (specially on Windows) and is very weak on both
user documentation.and tests.... read more

For this release, the parser is able to generate the header file for the errors (as an enum or using define) using a master XML file. The doxygen
comments are not yet embedded in the header file and, of course, there is no code to access the error messages.

The main goal of this release is to publish the format of the XML, the DTD (Document Type Definition) and to get comments or suggestions on it (see the files DTD/errorParser.dtd and DTD/example_vdsf.xml). ... read more