1.1 --- a/docs/wiki/History Mon Jun 28 00:13:11 2021 +0200
1.2 +++ b/docs/wiki/History Mon Jun 28 22:29:21 2021 +0200
1.3 @@ -71,7 +71,7 @@
1.4 == Current Work ==
1.5
1.6 It was with such realisations that a new project was effectively born.
1.7 -Tentatively called "!PythonLight" but renamed to "Lichen" as the code matured,
1.8 +Tentatively called "PythonLight" but renamed to "Lichen" as the code matured,
1.9 the objectives now involved a simpler processing framework that merely
1.10 attempted to catalogue structure members, to determine the origins of such
1.11 members, and to record data flow within namespaces in order to determine
2.1 --- a/docs/wiki/Toolchain Mon Jun 28 00:13:11 2021 +0200
2.2 +++ b/docs/wiki/Toolchain Mon Jun 28 22:29:21 2021 +0200
2.3 @@ -73,12 +73,12 @@
2.4 which the `parser` module effectively is (as would the `ast` module also be if
2.5 it were used here), with it typically being implemented as an extension module
2.6 in a non-Python language (in C for CPython, in Java for Jython, and so on).
2.7 -Fortunately, the !PyPy project implemented their own parsing module,
2.8 -`pyparser`, that is intended to be used within the !PyPy environment together
2.9 -with their own `ast` equivalent, but it has been possible to rework `pyparser`
2.10 -to produce representations that are compatible with the `compiler` package,
2.11 -itself being modified in various ways to achieve compatibility (and also to
2.12 -provide various other conveniences).
2.13 +Fortunately, the [[http://pypy.org/|PyPy]] project implemented their own
2.14 +parsing module, `pyparser`, that is intended to be used within the PyPy
2.15 +environment together with their own `ast` equivalent, but it has been possible
2.16 +to rework `pyparser` to produce representations that are compatible with the
2.17 +`compiler` package, itself being modified in various ways to achieve
2.18 +compatibility (and also to provide various other conveniences).
2.19
2.20 == Program Analysis ==
2.21