Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
630a63ca
Commit
630a63ca
authored
Aug 01, 2001
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix description of buffer_info(), and add a note that there is a better
way... This closes SF bug #444842.
parent
5a99e0ca
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
6 deletions
+15
-6
Doc/lib/libarray.tex
Doc/lib/libarray.tex
+15
-6
No files found.
Doc/lib/libarray.tex
View file @
630a63ca
...
...
@@ -68,12 +68,21 @@ Append a new item with value \var{x} to the end of the array.
\begin{methoddesc}
[array]
{
buffer
_
info
}{}
Return a tuple
\code
{
(
\var
{
address
}
,
\var
{
length
}
)
}
giving the current
memory address and the length in bytes of the buffer used to hold
array's contents. This is occasionally useful when working with
memory address and the length in elements of the buffer used to hold
array's contents. The size of the memory buffer in bytes can be
computed as
\code
{
\var
{
array
}
.buffer
_
info()[1] *
\var
{
array
}
.itemsize
}
. This is occasionally useful when working with
low-level (and inherently unsafe) I/O interfaces that require memory
addresses, such as certain
\cfunction
{
ioctl()
}
operations. The returned
numbers are valid as long as the array exists and no length-changing
operations are applied to it.
addresses, such as certain
\cfunction
{
ioctl()
}
operations. The
returned numbers are valid as long as the array exists and no
length-changing operations are applied to it.
\strong
{
Note:
}
When using array objects from code written in C or
\Cpp
{}
(the only way to effectively make use of this information), it
makes more sense to use the buffer interface supported by array
objects. This method is maintained for backward compatibility and
should be avoided in new code. The buffer interface is documented in
the
\citetitle
[../api/newTypes.html]
{
Python/C API Reference Manual
}
.
\end{methoddesc}
\begin{methoddesc}
[array]
{
byteswap
}{}
...
...
@@ -174,7 +183,7 @@ string if the \var{typecode} is \code{'c'}, otherwise it is a list of
numbers. The string is guaranteed to be able to be converted back to
an array with the same type and value using reverse quotes
(
\code
{
``
}
), so long as the
\function
{
array()
}
function has been
imported using
\
samp
{
from array import array
}
. Examples:
imported using
\
code
{
from array import array
}
. Examples:
\begin{verbatim}
array('l')
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment