pl/_
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated README; removed awkward joke, typo and explained the last part a bit

Browse Source
This commit is contained in:
Veit Heller
2015-02-20 21:40:59 +01:00
parent 9bbc59b6e5
commit d11ef52c6c
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -17,9 +17,6 @@ ____ _ ____ ____ __ _ ____ _ _ ___ _____ _____ _ ______
____ __ _ ____ __ _ ______
```
As you can see, it uses very advanced and fancy features of modern linguistics
to model the human language exactly in code.
As in mames' original version, you can create such a __script__ easily:
* __script__(YourCodeAsAStringHere) will encode it raw
@@ -32,7 +29,7 @@ _. Cool, huh?
Please note that the file you are importing is either an `.us` file or import
it by the fully qualified name(e.g. `import _.py`). This is to avoid confusion
with actual python modules. I can bring back the feature of including Python
modules, if you want me too, though.
modules, if you want me to, though.
The idea behind it is using Pythons import hooks to achieve something similar
to mames' original script, only that it works the opposite way.
@@ -46,4 +43,5 @@ Why is the code so ugly?
------------------------
That is due to me wanting the encoding and decoding be kept as close as possible
to the original, even if the module has a completely different structure.
to the original, even if the module has a completely different structure, which
means that I reimplemented a few Ruby functions from the Ruby standard in Python.