Guido van Rossum wrote: > > > Why C? Implement it in Python and freeze the sucker. > >=20 > > size and performance. exception classes are installed > > during initialization of the python interpreter, and they > > all need to be made available for C code anyway. > >=20 > > (in fact, the new code isn't that much larger than the > > code needed to copy stuff from exceptions.py) >=20 > Actually, in this case, I'd vote for C too. My reason is stability. > The process to freeze exceptions.py into the core will always be more > fragile than the process to compile C code. incomplete proof-of-concept implementation available here. see webpage and FIXME's in the code for more info: http://w1.132.telia.com/~u13208596/exceptions.htm </F>
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