From: Ulya Trofimovich Date: Wed, 6 Apr 2016 10:14:11 +0000 (+0100) Subject: Updated re2c description on homepage. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ddf72f800802ea1651fffb2631ddf9f4fc8bd676;p=re2c Updated re2c description on homepage. --- diff --git a/src/index.rst b/src/index.rst index cd8389fc..336e2b7c 100644 --- a/src/index.rst +++ b/src/index.rst @@ -19,23 +19,20 @@ Its key features are: It's because re2c generates minimalistic hard-coded state machine (as opposed to full-featured table-based lexers). -* Flexible API: the generated code can be wired into virtually any environment. - Instead of exposing traditional ``yylex()`` style API, re2c exposes its internals. - This gives you several opportunities. - First, you can avoid unnecessary overhead: drop useless runtime checks, do inplace lexing, etc. - Second, you can adjust lexer to your particular input model. - Third, you can make all sorts of strange hacks. - Of course, this means that you have to be careful: - with great power comes great responsibility. - Be sure to take a look at `examples `_, - they cover a lot of real-world cases and shed some light on dark corners of re2c API. - -* `Warnings `_ (static analyses): - re2c warns you when your code is bad and suggests a fix. - -* `Autognerated tests `_ (dynamic analyses): - re2c generates test program together with the input data. - The generated input has very good coverage. +* Flexible API: one can `configure `_ + or even `completely override `_ + the way re2c generates code. + Programmers can adjust lexer to a particular input model, + avoid unnecessary overhead (drop useless runtime checks, do inplace lexing, etc.) + and make all sorts of hacks. + `Examples `_ cover many real-world cases and shed some light on dark corners of re2c API. + +* Efficient `Unicode support `_ + (code points are compiled into executable finite-state machines). + +* `Warnings `_. + +* `Autognerated tests `_ with a very good coverage. * `License `_ (public domain).