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

Showing content from https://mail.python.org/pipermail/python-dev/2002-July/027156.html below:

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

• Previous message: [Python-Dev] pre-PEP: The Safe Buffer Interface
• Next message: [Python-Dev] pre-PEP: The Safe Buffer Interface
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> > Could also just have one acquire function that indicates whether it
> > is read-write or read-only via a return parameter.
> 
> That loses the (weak) symmetry with the existing API.
> 

There's nothing a client expecting a read/write pointer could
do with a read only pointer IMO.

> > Is write-only ever useful?
> 
> No, write implies read.

Should it be named getfixedreadwritebuffer then?

Thomas

• Previous message: [Python-Dev] pre-PEP: The Safe Buffer Interface
• Next message: [Python-Dev] pre-PEP: The Safe Buffer Interface
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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