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/027191.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 InterfaceScott Gilbert xscottg@yahoo.com
Wed, 31 Jul 2002 17:17:49 -0700 (PDT)
--- Greg Ewing <greg@cosc.canterbury.ac.nz> wrote:
> 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?
> 

That is the proposal.  The get methods are the legacy (non-fixed)
interface.





Cheers,
    -Scott


__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com



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