Janne Blomqvist wrote:
+For Boolean (@code{LOGICAL}) arguments, please note that GCC expects
+only the integer value 0 and 1. If a GNU Fortran @code{LOGICAL}
+variable contains another integer value, the result is undefined.
+As some other Fortran compilers use @math{-1} for @code{.TRUE.},
+extr
On Mon, Apr 8, 2013 at 5:38 PM, Tobias Burnus wrote:
> Dear all,
>
> attached is an updated version of the patch, which address the raised issues
> and some minor problems and omissions I found.
>
> OK for the trunk?
+For Boolean (@code{LOGICAL}) arguments, please note that GCC expects
+only the
Dear all,
attached is an updated version of the patch, which address the raised
issues and some minor problems and omissions I found.
OK for the trunk?
Tobias
2013-04-08 Tobias Burnus
* gfortran.texi (KIND Type Parameters,
Internal representation of LOGICAL variables): Add crossrefs.
(
On Sat, Mar 30, 2013 at 9:50 PM, Tobias Burnus wrote:
> Janne Blomqvist wrote:
>> +For procedures and variables declared in the specification space of a
>> +module, the name is formed by @code{__}, followed by the lower-cased
>> +module name, @code{_MOD_}, and the lower-cased Fortran name. Note t
Janne Blomqvist wrote:
Thanks for the patch! Comments below:
+For logical types, please note that the Fortran standard only guarantees
+interoperability between C99's @code{_Bool} and Fortran's @code{C_Bool}-kind
+logicals and C99 defines that @code{true} has the value 1 and @code{false}
+the va
On Fri, Mar 29, 2013 at 8:42 PM, Tobias Burnus wrote:
> Ups - I attached the wrong patch (same file name, wrong directory).
> Hopefully, this one is the correct one.
>
> Tobias
>
> Am 29.03.2013 19:40, schrieb Tobias Burnus:
>
>> Dear all,
>>
>> the attached patch attempts to document gfortran's n
Ups - I attached the wrong patch (same file name, wrong directory).
Hopefully, this one is the correct one.
Tobias
Am 29.03.2013 19:40, schrieb Tobias Burnus:
Dear all,
the attached patch attempts to document gfortran's naming and argument
passing convention when Bind(C) is not used.
While