This project is read-only.

Gardens Point LEX version 1.1.5

Rating:        Based on 3 ratings
Reviewed:  3 reviews
Downloads: 1027
Released: Nov 1, 2010
Updated: Nov 1, 2010 by k_john_gough
Dev status: Stable Help Icon

Recommended Download

application, 613K, uploaded Nov 1, 2010 - 628 downloads

Other Available Downloads

Documentation gplex.pdf
documentation, 578K, uploaded Nov 1, 2010 - 308 downloads
Documentation gplex-changelog.pdf
documentation, 29K, uploaded Nov 1, 2010 - 91 downloads

Release Notes

The main distribution is a zip file. This contains the binary executable, documentation, source code and the examples.


Version 1.1.5 corrects ar error in the handling of literal strings in regular expressions. The error messages associated with malformed literal strings have been improved, and c# code fragments can use verbatim literal strings.
A complete changelog is available as a separate documentation file.

Source Code

The distribution contains a complete VS2008 project for the application. However the latest code revisions are always available via the source code tab of this page.


Documentation is included in the zip archive, but is also available separately from this download page.
The main documentation is once again a single file. It now includes hyperlinked figure references, table of contents and index.
The documentation also describes the examples in the archive.

Reviews for this release

I agreed with the first reviewer. The tool is far from the perfect. In some cases tool crashes for no obvious reason. But it can generate some kind of simple lexers. Any attempts to add multiply state conditions is failed so far. Also I would expect a little bit more C#-like from the generated scanner interface, instead of the old-fashion C-like (type safe tokens, exceptions etc.).
by peter_azo on Feb 4, 2011 at 7:20 PM
Indispensable tool (along with GPPG). Yes, it has it's own regular expression engine, and for good reason (I howled when I read that last review).
by qhalid on Nov 26, 2010 at 10:36 AM
Two major issues: 1.) The author wrote their own regex engine of sorts, which basically makes it impossible to debug anything -- the engine is incomplete and will randomly crash the console app, work incorrectly, or complain about non-existent errors. 2.) The program does not read unicode files -- Visual Studio converts text files to unicode by default. After 5 hours? I'll pass for now -- thanks!
by AtomicDirtBike on Nov 20, 2010 at 12:43 PM