diff options
| author | Fred Drake <fdrake@acm.org> | 2001-10-20 04:24:09 (GMT) |
|---|---|---|
| committer | Fred Drake <fdrake@acm.org> | 2001-10-20 04:24:09 (GMT) |
| commit | 0aa811c527372fbee0e20192bba3cf343a744e08 (patch) | |
| tree | ab0d86073c96b664d6b9d87ea84cdb8cdb263755 /Doc/lib/libarray.tex | |
| parent | 64a5aaf05ca20bdbd72c30fa0cfdda2ae9a347d9 (diff) | |
| download | cpython-0aa811c527372fbee0e20192bba3cf343a744e08.zip cpython-0aa811c527372fbee0e20192bba3cf343a744e08.tar.gz cpython-0aa811c527372fbee0e20192bba3cf343a744e08.tar.bz2 | |
Use the \note and \warning macros where appropriate.
Diffstat (limited to 'Doc/lib/libarray.tex')
| -rw-r--r-- | Doc/lib/libarray.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/lib/libarray.tex b/Doc/lib/libarray.tex index 868770e..ac02b87 100644 --- a/Doc/lib/libarray.tex +++ b/Doc/lib/libarray.tex @@ -77,12 +77,12 @@ 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 +\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}. +the \citetitle[../api/newTypes.html]{Python/C API Reference Manual}.} \end{methoddesc} \begin{methoddesc}[array]{byteswap}{} |