VimPlug/jedi-fork
1
0
Fork 0
forked from VimPlug/jedi
Code Pull Requests Activity

docstring update for parsing_representation

Browse Source
This commit is contained in:
David Halter
2013-02-07 18:19:22 +01:00
parent 0eeb1036ac
commit 6d2d23cd78
1 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
jedi/parsing_representation.py
View File

@@ -8,13 +8,12 @@ inherited. It's used by ``Function``, ``Class``, ``Flow``, etc. A ``Scope`` may
have ``subscopes``, ``imports`` and ``statements``. The entire parser is based have ``subscopes``, ``imports`` and ``statements``. The entire parser is based
on scopes, because they also stand for indentation. on scopes, because they also stand for indentation.
One strange thing about the parser is that ``Array`` is two dimensional. This One special thing:
has been caused by the fact that each array element can be defined by
operations: ``[1, 2+33]``. So I chose to use a second dimension for ``2+33``, ``Array`` values are statements. But if you think about it, this makes sense.
where each element would lie in the array like this: ``[2, '+', 33]``. In the ``[1, 2+33]`` for example would be an Array with two ``Statement`` inside. This
future it might be useful to use Statements there, too (remove those crappy two is the easiest way to write a parser. The same behaviour applies to ``Param``,
dimensional arrays). This is also how ``Param`` works. Every single ``Param`` which is being used in a function definition.
is a ``Statement``.
.. todo:: remove docstr params from Scope.__init__() .. todo:: remove docstr params from Scope.__init__()