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

Scott Gilbert xscottg@yahoo.com
Wed, 31 Jul 2002 08:28:32 -0700 (PDT)


--- Guido van Rossum <guido@python.org> wrote:
>
> Based on the example of mmap (which can be closed at any time) I
> agree that the fixed buffer interface needs to have "get"
> and "release" methods (please pick better names).  Maybe Thomas can
> update PEP 298.
> 

Wow, the tides have turned.  Fair enough.

I think Neil put forth the names "acquire" and "release".  So how about

        typedef struct {
                getreadbufferproc bf_getreadbuffer;
                getwritebufferproc bf_getwritebuffer;
                getsegcountproc bf_getsegcount;
                getcharbufferproc bf_getcharbuffer;
                /* fixed buffer interface functions */
                acquirereadbufferproc bf_acquirereadbuffer;
                acquirewritebufferproc bf_acquirewritebuffer;
                releasebufferproc bf_releasebuffer;
        } PyBufferProcs;

Whatever the actual names, should there be a bf_releasereadbuffer and
bf_releasewritebuffer?  Or just the one bf_releasebuffer?  Could also just
have one acquire function that indicates whether it is read-write or
read-only via a return parameter.  Is write-only ever useful?




Cheers,
    -Scott


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