> It certainly wouldn't hurt to implement this, as it would provide some > practical implementation experience that would inform a PEP on the > subject. If it solves the mess with supporting extended call syntax, adding these opcodes might be a good idea. But as I said, for the normal (not extended) case, the existing CALL_FUNCTION opcode is the right thing to use unless you want things to slow down significantly. --Guido van Rossum (home page: http://www.python.org/~guido/)
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