Next | Query returned 3 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2014-12-31 14:58:32 by Thomas Klausner | Files touched by this commit (37)
Log message:
Improve EGG_NAME default to work for packages with '-' in their name.
Remove now unnecessary overrides in various packages.

Fix various problems while here, including marking packages as not ready
for python-3.x.
   2012-10-07 15:57:25 by Aleksej Saushev | Files touched by this commit (211)
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
Mark packages that don't or might probably not have staged installation.
   2010-08-02 23:35:05 by Kamel Derouiche | Files touched by this commit (4) | Imported package
Log message:
Import py26-plex-2.0.0 as wip/py-plex.

Plex is a Python module for constructing lexical analysers, or scanners.
Plex scanners have almost all the capabilities of the scanners generated by
GNU Flex, and are specified in a very similar way. Tokens are defined by regular
expressions, and each token has an associated action, which may be to return a
literal value, or to call an arbitrary function.

Plex is designed to fill a need that is left wanting by the existing Python
regular expression modules. If you've ever tried to use one of them for
implementing a scanner, you will have found that they're not really suited to
the task You can define a bunch of regular expressions which match your tokens
all right but you can only match one of them at a time against your input.
To match all of them at once, you have to join them all together into one big
r.e., but then you've got no easy way to tell which one matched. This is
the problem that Plex is designed to solve.

Another advantage of Plex is that it compiles all of the regular expressions
into a single DFA. Once that's done, the input can be processed in a time
proportional to the number of characters to be scanned, and independent of the
number or complexity of the regular expressions. Python's existing regular
expression matchers do not have this property.


Next | Query returned 3 messages, browsing 1 to 10 | previous