diff options
author | wfspotz@sandia.gov <wfspotz@sandia.gov@localhost> | 2007-08-03 21:21:10 +0000 |
---|---|---|
committer | wfspotz@sandia.gov <wfspotz@sandia.gov@localhost> | 2007-08-03 21:21:10 +0000 |
commit | 5bd291e93a4885d4d176f2675c68a4baae8a0c80 (patch) | |
tree | 4ac0c53a1da878b98c834069e6d5286a91849dd2 /numpy/doc/swig | |
parent | 66650bdd599110d55425467d5a99aba0a5c6026d (diff) | |
download | numpy-5bd291e93a4885d4d176f2675c68a4baae8a0c80.tar.gz |
In documentation, removed one of the reasons for not providing (out) typemaps, which turns out not to be true.
Diffstat (limited to 'numpy/doc/swig')
-rw-r--r-- | numpy/doc/swig/numpy_swig.html | 10 | ||||
-rw-r--r-- | numpy/doc/swig/numpy_swig.pdf | bin | 148220 -> 148245 bytes | |||
-rw-r--r-- | numpy/doc/swig/numpy_swig.txt | 8 |
3 files changed, 5 insertions, 13 deletions
diff --git a/numpy/doc/swig/numpy_swig.html b/numpy/doc/swig/numpy_swig.html index 90706ac84..6b2a750ef 100644 --- a/numpy/doc/swig/numpy_swig.html +++ b/numpy/doc/swig/numpy_swig.html @@ -634,13 +634,9 @@ cannot be avoided. Note that for these types of 1D typemaps, the <div class="section"> <h2><a class="toc-backref" href="#id7" id="output-arrays" name="output-arrays">Output Arrays</a></h2> <p>The <tt class="docutils literal"><span class="pre">numpy.i</span></tt> interface file does not support typemaps for output -arrays, for several reasons. First, C/C++ function return arguments -do not have names, so signatures for <tt class="docutils literal"><span class="pre">%typemap(out)</span></tt> do not include -names. This means that if <tt class="docutils literal"><span class="pre">numpy.i</span></tt> supported them, they would -apply to all pointer return arguments for the supported numeric -types. This seems too dangerous. Second, C/C++ return arguments are +arrays, for several reasons. First, C/C++ return arguments are limited to a single value. This prevents obtaining dimension -information in a general way. Third, arrays with hard-coded lengths +information in a general way. Second, arrays with hard-coded lengths are not permitted as return arguments. In other words:</p> <pre class="literal-block"> double[3] newVector(double x, double y, double z); @@ -1053,7 +1049,7 @@ possible.</p> </div> <div class="footer"> <hr class="footer" /> -Generated on: 2007-04-13 20:43 UTC. +Generated on: 2007-08-03 21:19 UTC. Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. </div> diff --git a/numpy/doc/swig/numpy_swig.pdf b/numpy/doc/swig/numpy_swig.pdf Binary files differindex aadcc9fe4..3e755b0ff 100644 --- a/numpy/doc/swig/numpy_swig.pdf +++ b/numpy/doc/swig/numpy_swig.pdf diff --git a/numpy/doc/swig/numpy_swig.txt b/numpy/doc/swig/numpy_swig.txt index d00ad6ff5..c8450045d 100644 --- a/numpy/doc/swig/numpy_swig.txt +++ b/numpy/doc/swig/numpy_swig.txt @@ -318,13 +318,9 @@ Output Arrays ------------- The ``numpy.i`` interface file does not support typemaps for output -arrays, for several reasons. First, C/C++ function return arguments -do not have names, so signatures for ``%typemap(out)`` do not include -names. This means that if ``numpy.i`` supported them, they would -apply to all pointer return arguments for the supported numeric -types. This seems too dangerous. Second, C/C++ return arguments are +arrays, for several reasons. First, C/C++ return arguments are limited to a single value. This prevents obtaining dimension -information in a general way. Third, arrays with hard-coded lengths +information in a general way. Second, arrays with hard-coded lengths are not permitted as return arguments. In other words:: double[3] newVector(double x, double y, double z); |