Jakub Wilk
7a2348e4cc
Fix typos
2024-01-19 23:20:13 +01:00
rocky
88e169adca
More verbiage on what we have and what's happened.
2021-12-27 16:28:28 -05:00
rocky
8deb940b21
Update and revise HISTORY
...
Remove some of the older history and put a link to that which is nos
recorded in decompyle-2.4's history.
2021-12-22 21:49:38 -05:00
R. Bernstein
4c4aa393df
Update HISTORY.md
2019-05-17 10:24:13 -04:00
rocky
b6d96929cb
Start simplifying higher-level API
2018-02-27 17:48:26 -05:00
rocky
b1cdbe1656
update history
2017-12-02 22:45:07 -05:00
rocky
6fee7fdfe3
Claan up 3.x custom MAKE_{FUNCTION,CLOSURE} rules
2017-11-29 21:09:50 -05:00
rocky
2fc3886693
Small changes
2017-10-13 07:52:56 -04:00
rocky
7fed237077
History updates
2017-07-14 08:03:06 -04:00
R. Bernstein
b42c66e091
Update HISTORY.md
2017-04-29 22:32:16 -04:00
R. Bernstein
7755dddd94
Update HISTORY.md
2017-04-22 11:18:08 -04:00
R. Bernstein
ce1e841255
Update HISTORY.md
2017-04-22 11:15:45 -04:00
rocky
68f0f79030
History keeps gettting amended
2017-04-22 11:12:52 -04:00
rocky
4e05c741e3
grammar typo and add another test
2017-03-15 03:59:07 -04:00
rocky
545a46dffa
Correct spelling of Earley
2017-01-21 06:24:31 -05:00
rocky
1fc8ac4700
Interval order COME_FROMs in Python3
...
This bug had possibly caused lots of grammar pollution which may need
addressing.
We want to process COME_FROMs to the same offset to be in *descending*
order so we have the larger range or biggest instruction interval
last. (I think they are sorted in increasing order, but for safety
we sort them). That way, specific COME_FROM tags will match up
properly. For example, a "loop" with an "if" nested in it should have
the "loop" tag last so the grammar rule matches that properly
Adjust Python 3 grammar for more COME_FROM -> COME_FROM_LOOP. And
remove optional COME_FROM_LOOP where possible. Previously, the
optional-ness was a result of inner nestings gobbling up the
COME_FROM.
We'll probably want to go back and fix this up in Python2.
2016-09-26 09:26:51 -04:00
rocky
d1ef0bf21b
Update HISTORY and add link to it in README.md
2016-07-20 12:02:58 -04:00
rocky
04698f45cc
Update history. Note 2.5-2.6 deficiencies
...
Note Eloi Vanderbeken's contribution
2016-07-03 11:32:20 -04:00
rocky
06edeeeb46
Get ready for release 2.4.0
2016-05-18 12:46:23 -04:00
rocky
bdd7df6040
Python 2 loop scanner detection in Python 3
...
scanner*.py: Make scanner27 and scanner3 more aligned
Makefile: we can run py.test on Python 3.5
HISTORY.md: grammar changes
2016-05-16 13:40:55 -04:00
rocky
134b67d952
Misc small changes
...
Go over history yet again
code cleanups.
2016-05-16 10:15:55 -04:00
rocky
007328b353
Correct info on parser
2016-05-15 19:44:18 -04:00
rocky
378cca27da
Dan Pascu's contribution via Dan
2016-05-09 12:47:16 -04:00
rocky
f9dc797aa0
Another history tweak
2016-05-09 12:13:42 -04:00
rocky
8b9e0eca42
Some grammar cleanup
2016-05-09 11:58:05 -04:00
rocky
73461d323e
More small history tweaks
2016-05-09 05:34:01 -04:00
rocky
739ce7b1fd
Go over history yet again.
2016-05-08 16:44:17 -04:00
rocky
4a79082872
Fix 3.5 if..pass bug
...
Update HISTORY.MD to include Dan Pascu. Some minor doc corrections
2016-05-08 10:32:11 -04:00
rocky
9f7d36f8fb
Handle Ternary "or". Remove mention of uncompyle3
...
uncompyle3 removed per Mysterie's request
[Fixes Issue #5 ]
2016-04-07 07:18:46 -04:00
R. Bernstein
f25c9b45a4
Grammar fixes
2016-01-05 07:47:31 -05:00
rocky
6a49cd2c69
Bug in for loop with try. Add more of 2.7's COME_FROM statements.
...
spark.py: add tracing reduce rules. main: reduce cutsines.
Start history
2015-12-21 21:08:08 -05:00
