A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-August/027187.html below:

[Python-Dev] pre-PEP: The Safe Buffer Interface

[Python-Dev] pre-PEP: The Safe Buffer Interface [Python-Dev] pre-PEP: The Safe Buffer InterfaceGreg Ewing greg@cosc.canterbury.ac.nz
Thu, 01 Aug 2002 11:48:21 +1200 (NZST)
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?

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
greg@cosc.canterbury.ac.nz	   +--------------------------------------+



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