summaryrefslogtreecommitdiff
path: root/doc/source/f2py/getting-started.rst
diff options
context:
space:
mode:
authorPauli Virtanen <pav@iki.fi>2014-01-02 23:31:34 +0200
committerPauli Virtanen <pav@iki.fi>2014-01-02 23:31:34 +0200
commit3b3a531f9564d5696b3a50d41636b58d65ba1330 (patch)
tree72cd674c7e4474ded757eedc6dd5b83c3c372f90 /doc/source/f2py/getting-started.rst
parent6c7af638e760d3229f460cb7475548ef2a3a7ca9 (diff)
downloadnumpy-3b3a531f9564d5696b3a50d41636b58d65ba1330.tar.gz
DOC: f2py: more Numeric -> numpy updating
Diffstat (limited to 'doc/source/f2py/getting-started.rst')
-rw-r--r--doc/source/f2py/getting-started.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/source/f2py/getting-started.rst b/doc/source/f2py/getting-started.rst
index fca02307b..99c0112fc 100644
--- a/doc/source/f2py/getting-started.rst
+++ b/doc/source/f2py/getting-started.rst
@@ -95,11 +95,11 @@ Python the Fortran subroutine ``FIB`` is accessible via ``fib1.fib``::
F2PY implements basic compatibility checks between related
arguments in order to avoid any unexpected crashes.
- * When a Numpy array, that is Fortran contiguous and has a typecode
+ * When a Numpy array, that is Fortran contiguous and has a dtype
corresponding to presumed Fortran type, is used as an input array
argument, then its C pointer is directly passed to Fortran.
- Otherwise F2PY makes a contiguous copy (with a proper typecode) of
+ Otherwise F2PY makes a contiguous copy (with a proper dtype) of
the input array and passes C pointer of the copy to Fortran
subroutine. As a result, any possible changes to the (copy of)
input array have no effect to the original argument, as
@@ -111,7 +111,7 @@ Python the Fortran subroutine ``FIB`` is accessible via ``fib1.fib``::
[1 1 1 1 1 1 1 1]
Clearly, this is not an expected behaviour. The fact that the
- above example worked with ``typecode='d'`` is considered
+ above example worked with ``dtype=float`` is considered
accidental.
F2PY provides ``intent(inplace)`` attribute that would modify