micropython/micropython — pull request #313 by pfalcon (2014-02-21 01:32:57+00:00)
Title: parse: Implement hacky way to handle full range of small ints.

So, I proceeded to write testcases for varlen encoded small ints, and that's why I paid attention that parser has its own "small ints" which don't match normal "small ints". So, while my aim was to let people write a billion as a number in uPy, that still can't be done. OMG, let's work around it then, but see TODO below.

Parser has its own "small small ints", which unfortunately means that full
range of small ints are not available in lexical form. This issue is usually
masked by presence of long int, but without them, it's not possible to write
biggish numbers in a Python program.

To work that around, CONST_INT node is overloaded with special encoding for
full-range small ints, which eventually propagated to bytecode properly, as
LOAD_CONST_SMALL_INT.

TODO: Ideally, parser should not have its own "small int" type, and instead
all parts of interpreter should use single consistent type (even if that on
parser side requires more fat representation) - dealing with types fragmented
without real need is a chore.