[Bug fortran/19101] missing & in character continuation not caught

2006-04-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2006-04-07 21:20 --- Fixed now on 4.1.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/19101] missing & in character continuation not caught

2006-04-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-04-07 21:12 --- Subject: Bug 19101 Author: jvdelisle Date: Fri Apr 7 21:12:41 2006 New Revision: 112764 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112764 Log: 2006-04-07 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug fortran/19101] missing & in character continuation not caught

2006-04-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-04-07 21:07 --- Subject: Bug 19101 Author: jvdelisle Date: Fri Apr 7 21:07:52 2006 New Revision: 112763 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112763 Log: 2006-04-07 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug fortran/19101] missing & in character continuation not caught

2006-03-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-03-15 07:08 --- Subject: Bug 19101 Author: jvdelisle Date: Wed Mar 15 07:08:06 2006 New Revision: 112079 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112079 Log: 2006-03-14 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug fortran/19101] missing & in character continuation not caught

2006-03-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2006-03-15 07:03 --- Subject: Bug 19101 Author: jvdelisle Date: Wed Mar 15 07:03:20 2006 New Revision: 112078 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112078 Log: 2006-03-14 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug fortran/19101] missing & in character continuation not caught

2006-03-11 Thread patchapp at dberlin dot org
--- Comment #9 from patchapp at dberlin dot org 2006-03-12 05:15 --- Subject: Bug number PR19101 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/2006-03/msg00691.html -- http://gcc.gnu.org/bugzilla/sh

[Bug fortran/19101] missing & in character continuation not caught

2006-03-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-03-09 06:08 --- A revised patch has been submitted that does what might be expected and issues a warning on -pedantic if the ampersand is missing in a continued character constant. -- http://gcc.gnu.org/bugzilla/show_bug.cgi

[Bug fortran/19101] missing & in character continuation not caught

2006-03-07 Thread patchapp at dberlin dot org
--- Comment #7 from patchapp at dberlin dot org 2006-03-08 07:35 --- Subject: Bug number PR19101 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/2006-03/msg00415.html -- http://gcc.gnu.org/bugzilla/sh

[Bug fortran/19101] missing & in character continuation not caught

2006-03-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-03-06 06:23 --- I have found the fix for this. It is simple. Do we want to allow the missing & and then give an error on -pedantic? Intel allows the missing & and continues at the next non blank character. How strict shall we

[Bug fortran/19101] missing & in character continuation not caught

2006-02-21 Thread jvdelisle at gcc dot gnu dot org
-- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |jvdelisle at gcc dot gnu dot |dot org

[Bug fortran/19101] missing & in character continuation not caught

2004-12-28 Thread tobi at gcc dot gnu dot org
--- Additional Comments From tobi at gcc dot gnu dot org 2004-12-28 19:19 --- I have a fix which issues the same error twice. Unfortunately, continuation lines are eaten in the scanner, and there is no real support for emitting errors from the scanner, as the same line may be rescanned

[Bug fortran/19101] missing & in character continuation not caught

2004-12-27 Thread tobi at gcc dot gnu dot org
--- Additional Comments From tobi at gcc dot gnu dot org 2004-12-27 21:47 --- Actually, my misleading reference is by the same authors the same as Erik's, it's the "Fortran 90 Handbook". Looks like they got it wrong. I think I have a fix, it wasn't too hard :-) -- http://gcc.gnu.org

[Bug fortran/19101] missing & in character continuation not caught

2004-12-27 Thread tobi at gcc dot gnu dot org
--- Additional Comments From tobi at gcc dot gnu dot org 2004-12-27 21:41 --- That's weird. I wrote some of this originally, and I was sure that this has to be interpreted in the way Erik quotes it. I double-checked the F95 and F2K standards and they both agree with Thomas, but I have a

[Bug fortran/19101] missing & in character continuation not caught

2004-12-25 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2004-12-25 09:31 --- (In reply to comment #1) The latest version of the F95 draft standard (isn't the world of coypyrighted standards wonderful?) states # If a character context is to be continued, the "&" shall be # the l

[Bug fortran/19101] missing & in character continuation not caught

2004-12-24 Thread eedelman at acclab dot helsinki dot fi
--- Additional Comments From eedelman at acclab dot helsinki dot fi 2004-12-25 00:41 --- I think the result given by gfortran is correct. Quote from "Fortran 95 handbook" by Adams, Brainerd et al., section 3.3.1.1 """ To continue a character constant so that the continued line is inden

[Bug fortran/19101] missing & in character continuation not caught

2004-12-21 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Keywords||accepts-invalid, diagnostic http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19101