A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-April/035070.html below:

[Python-Dev] should sre.Scanner be exposed through re and documented?

[Python-Dev] should sre.Scanner be exposed through re and documented? [Python-Dev] should sre.Scanner be exposed through re and documented?"Martin v. Löwis" martin@v.loewis.de
Fri, 25 Apr 2003 21:32:26 +0200
Skip Montanaro wrote:
> While moving tests from test_sre to test_re I stumbled upon a simple test
> for sre.Scanner.  This looks fairly cool.  Should it be exposed through re
> and documented?

I think /F did not consider it ready for general consumption. I believe
the approach is cool, but the API would still leave features to be 
desired. In practical compiler construction, I usually copy the 
approach, and duplicate it - that gives a very efficient and readily 
comprehensible scanner.

IOW, I would leave it where it is: As a masterpiece of work to get 
inspiration from, but not as a tool to give out to anybody.

Regards,
Martin




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4