[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-09-24 Thread tobi at gcc dot gnu dot org
--- Comment #8 from tobi at gcc dot gnu dot org 2007-09-24 21:15 --- Subject: Bug 33269 Author: tobi Date: Mon Sep 24 21:15:00 2007 New Revision: 128732 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=128732 Log: PR fortran/33269 fortran/ * io.c (check_format_string): Move NULL

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-09-24 Thread patchapp at dberlin dot org
--- Comment #9 from patchapp at dberlin dot org 2007-09-24 21:48 --- Subject: Bug number PR33269 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-09/msg01797.html --

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-09-24 Thread tobi at gcc dot gnu dot org
--- Comment #10 from tobi at gcc dot gnu dot org 2007-09-25 05:39 --- Fixed. -- tobi at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-09-22 Thread tobi at gcc dot gnu dot org
--- Comment #7 from tobi at gcc dot gnu dot org 2007-09-22 12:53 --- Created an attachment (id=14244) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14244action=view) Unfinished patch Here's a patch. I won't have time for the final cosmetics for a few days to come, so I'm posting

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-09-02 Thread tobi at gcc dot gnu dot org
-- tobi at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |tobi at gcc dot gnu dot org |dot org

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-09-02 Thread tobi at gcc dot gnu dot org
--- Comment #4 from tobi at gcc dot gnu dot org 2007-09-02 18:27 --- (In reply to comment #3) No, the syntax is: READ format[, io-list] and ('f.3.3') as a constant-string expression for the format; this is similar to PRINT ('f3.3'), a. This should be distinguished from:

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-09-02 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2007-09-02 18:42 --- (In reply to comment #4) if the first item after the ( is a default-char-expression (constant or not) and there is no ...= (e.g. fmt=) in there, then it is also a READ format statement. This is wrong. In

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-09-02 Thread tobi at gcc dot gnu dot org
--- Comment #6 from tobi at gcc dot gnu dot org 2007-09-02 18:48 --- (In reply to comment #5) (In reply to comment #4) if the first item after the ( is a default-char-expression (constant or not) and there is no ...= (e.g. fmt=) in there, then it is also a READ format

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-08-31 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-08-31 14:16 --- Actually, all of the following is affected. The last one fails before due to PR 33268. print ('a'), 'Hello' write(*,('a')) 'Hello' read (*,('f3.3')) a read ('f3.3'), a end --

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-08-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-08-31 19:47 --- gfortran does catch these at run time. Also, the last case, read ('f3.3'), a, does give a legitimate error: read ('f3.3'), a 1 Error: UNIT specification at (1) must be an INTEGER expression or a CHARACTER

[Bug fortran/33269] Diagnose missing ( in PRINT ('a'),

2007-08-31 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-08-31 20:02 --- gfortran does catch these at run time. Well, at compile time is nicer ;-) Also, the last case, read ('f3.3'), a, does give a legitimate error: read ('f3.3'), a 1 Error: UNIT specification at (1) must be