--- Comment #6 from dfranke at gcc dot gnu dot org 2009-12-08 21:01 ---
(In reply to comment #4)
> Maybe I could change this warning into an error even for non-standard
> conforming mode in case the length or a kind parameter differs. What
> do you think?
I assume, this happened at so
--- Comment #5 from dfranke at gcc dot gnu dot org 2009-12-08 20:58 ---
*** Bug 34527 has been marked as a duplicate of this bug. ***
--
dfranke at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #4 from domob at gcc dot gnu dot org 2008-09-08 06:36 ---
IIRC, this behaviour is due to a patch I submitted some time ago. Maybe I
could change this warning into an error even for non-standard conforming mode
in case the length or a kind parameter differs. What do you thin
--- Comment #3 from dominiq at lps dot ens dot fr 2008-09-07 22:06 ---
With -std=f95 all the gfortran versions I have reject the code with:
[ibook-dhum] f90/bug% gfc -std=f95 pr37412.f90
pr37412.f90:3.17:
character(1) st
1
Error: Symbol 'st' at (1) already has basic t
--- Comment #2 from burnus at gcc dot gnu dot org 2008-09-07 21:35 ---
(In reply to comment #1)
> Warning: Symbol 'st' at (1) already has basic type of CHARACTER
I think one should print here an error as the LEN type parameter is different.
The same issue exists for the KIND type para
--- Comment #1 from dominiq at lps dot ens dot fr 2008-09-07 21:15 ---
Confirmed with 4.2.3 and 4.3.2, with 4.4.0 (trunk) I get:
[ibook-dhum] f90/bug% gfc -Wall pr37412.f90
pr37412.f90:3.17:
character(1) st
1
Warning: Symbol 'st' at (1) already has basic type of CHARA
