From: "Greg Ewing" <greg@cosc.canterbury.ac.nz> > Scott Gilbert <xscottg@yahoo.com>: > > > getreadbufferproc bf_getreadbuffer; > > getwritebufferproc bf_getwritebuffer; > > > > acquirereadbufferproc bf_acquirereadbuffer; > > acquirewritebufferproc bf_acquirewritebuffer; > > Is there really a need for both "get" and "acquire" > methods? Surely if an object requires locking, it > always requires locking, so why can't the "get" > functions simply include the locking operation > if they need it? Backward compatibility. If we change the array object to enter a locked state when getreadbuffer() is called, it would be surprising. Thomas
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