155 Commits

Author	SHA1	Message	Date
rocky	fa84f4277a	WIP deal with JUMP_IF_{TRUE,FALSE} vs with POP version	2016-06-24 20:06:10 -04:00
rocky	fa7d8f955a	WIP Python-2.6 but don't remove opcodes ... The scheme for turning 2.6 bytecode into 2.7 psuedo bytecode I think is a lose. I won't work for fragment handling. Instead, change the grammar and syntax rules This also has the benefits: * We see how code generation changed over releases by looking at grammar and semantic rules rather than arbitrary code * We can better assocate with what's running (in a sense this is a restatement of broken fragment handling) * With the right structure in place we are in a better position to handle 2.5, 2.4, etc. That is, after a while, the incremental changes to get say from python 2.3 bytecode to python 2.7 are great. Conflicts: uncompyle6/parsers/astnode.py	2016-06-24 18:15:59 -04:00
rocky	982a6010a1	WIP 2.6 redo bytecode handling ... Don't try to convert 2.6 bytecode to 2.7 psuedo bytecode. Instead adjust grammar and semantic actions. Down the line we should to segregate version changes in semantic code better.	2016-06-24 09:23:30 -04:00
rocky	724faf9a3a	Go over grammars.. ... * Reduce duplication * Remove unused grammar rules * Add grammar checking when parsers run as standalone	2016-06-17 22:59:17 -04:00
rocky	3da4c9ce77	Start custom grammar for 2.6 and ... ... fix a python 2.6.9 deparse with lc if+and+not	2016-06-02 19:16:27 -04:00