Janus Weil wrote:
In any case, for those two, it does not trigger but one
gets later (resolve?) the error:
Error: Allocate-object at (1) must be ALLOCATABLE or a POINTER
Then I guess one can just remove the FIXME.
That's fine with me.
Regarding the error:
Error: Allocate-object at (1) is neither a nonprocedure pointer nor an
allocatable variable
I wonder whether one should put parentheses around nonprocedure; I tend to
misread it; namely:
Error: Allocate-object at (1) is neither a (nonprocedure) pointer nor an
allocatable variable
One could also use "... is neither a data pointer ...", which should
have the same meaning
I think that's better.
By the way, I wonder whether one shouldn't unify the error message
between match.c and resolve.c; there is no real reason to have two
different strings.
A new version of the patch is attached, which removes the FIXME and
changes the wording of the error message (will re-check for
regressions due to the changed wording).
Thanks!
Tobias
