From 81bdad0401275890d31bf2edc274fdb8e9ef950a Mon Sep 17 00:00:00 2001 From: Alexander Heger Date: Sat, 12 Sep 2015 12:30:52 +1000 Subject: BUG: allow extension of common blocks in numpy.f2py Lack of this feature resulted in the generation of incorrect *.pyf files. For example, the pyf file created by: subroutine sub3 (some arguments) real a, b, c, d common /coeff/ a, b common /coeff/ c, d return end Should contain both common statements the declaration of all four variables a, b, c, and d. Closes #5876. --- doc/source/f2py/signature-file.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'doc/source') diff --git a/doc/source/f2py/signature-file.rst b/doc/source/f2py/signature-file.rst index cfc35ebda..54b8736f1 100644 --- a/doc/source/f2py/signature-file.rst +++ b/doc/source/f2py/signature-file.rst @@ -178,12 +178,13 @@ Common block statements: := [ ( ) ] [ , ] - One ``python module`` block should not contain two or more - ``common`` blocks with the same name. Otherwise, the latter ones are - ignored. The types of variables in ```` are defined - using ````. Note that the corresponding - ```` may contain array specifications; - then you don't need to specify these in ````. + If a ``python module`` block contains two or more ``common`` blocks + with the same name, the variables from the additional declarations + are appened. The types of variables in ```` are + defined using ````. Note that the + corresponding ```` may contain array + specifications; then you don't need to specify these in + ````. Other statements: The ```` part refers to any other Fortran language -- cgit v1.2.1