Guido van Rossum wrote: > Tav is interested in using this on app engine, which doesn't care > about segfaults -- the process is simply restarted, nobody gains > access to information they shouldn't have. App engine does care about > overwriting memory, That doesn't make sense -- how can something not care about segfaults, but care about memory overwriting? If something is capable of causing a segfault, you can't be sure it won't just corrupt memory in some way that doesn't segfault but causes some other problem. -- Greg
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