> BTW, do we actually need *any* auxiliary data structure here? Looks > to me like all these giant pylist thingies could be tossed in favor > of making shallow copies of the input ifdlist etc list arguments. > The giant pylists don't *appear* to accomplish anything except cache > the result of a PyObject_AsFileDescriptor() call per object. But if > that's not an expensive call (doesn't look expensive to me), it's > not worth all this trouble no matter how spelled. Yes, I think we do need this. PyObject_AsFileDescriptor() calls the fileno() method which could be a Python call. Maybe we could use a more sophisticated construct where we use a short array allocated on the stack for lists of fewer than 100 (say) files but use malloc for larger ones? --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