Prev: minor typo in The Fortran 2003 Handbook?
Next: Questions on reuse of FORMAT statements and newer I/O options such as ACCESS='STREAM'
From: Tobias Burnus on 29 Dec 2009 14:23
On 27 December 2009 09:32, James Van Buskirk wrote:
> In reading the gfortran manual, it says:
>> Description:
>> ALLOCATED(ARRAY) checks the status of whether X is allocated.
>
> Now, I can envision two problems with this:
> 1) It's probably checking whether ARRAY is allocated, not X.
> 2) There is no provision given for the SCALAR version.

Thanks for the bug reports; however, I like to rejoin Steve and Steven:
Please report directly to GCC - best to bugzilla, but the fortran(a)gcc is
also more suitable. Those channels are not only more appropriate but and
foremost: Only bugs which are in bugzilla won't get lost.

Regarding the issue that untouched scalar allocatables get reported as
allocated: That is a known but still unfixed problem - targeted to be
fixed for the GCC 4.5 release; see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41872

The SCALAR= issue is new and was missed when implementing scalar
allocatables. I have filled a PR to track this. The obvious work-around
is to simply use ALLOCATED(var) rather than ALLOCATED(scalar=var); see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42546

I have not yet looked at the documentation issues, but I think Steve's
patch fixes most (all?) of those.

Tobias
First  |  Prev  | 
Pages: 1 2
Prev: minor typo in The Fortran 2003 Handbook?
Next: Questions on reuse of FORMAT statements and newer I/O options such as ACCESS='STREAM'