Jeremy Hylton writes: > You made a change to the syntax error generation code last August. > I don't understand what the code is doing. It appears that the code > you added is redundant, but it's hard to tell for sure because > responsbility for generating well-formed SyntaxErrors is spread > across several files. This is probably the biggest reason it's taken so long to get things into the ballpark! > The code you added in pythonrun.c, line 1084, in err_input(), starts > with the test (v != NULL): I've ripped all that out. > Can you shed any light? Was this all the light you needed? Or was there something deeper that I'm missing? -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4