[Bug fortran/45108] Namelist read: Not aborted when reading from STDIN

2010-08-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2010-08-19 20:32 --- Closing -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|ASS

[Bug fortran/45108] Namelist read: Not aborted when reading from STDIN

2010-08-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2010-08-19 20:28 --- Subject: Bug 45108 Author: jvdelisle Date: Thu Aug 19 20:28:09 2010 New Revision: 163387 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=163387 Log: 2010-08-19 Jerry DeLisle PR libfortran/45108

[Bug fortran/45108] Namelist read: Not aborted when reading from STDIN

2010-08-19 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2010-08-19 09:04 --- (In reply to comment #6) > This patch will generate an error. If IOSTAT or IOMSG is used, the read will > continue in the loop after an error, but the error status variables will be > set > so that one will know an

[Bug fortran/45108] Namelist read: Not aborted when reading from STDIN

2010-08-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2010-08-19 03:52 --- Created an attachment (id=21516) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21516&action=view) Proposed patch This patch will generate an error. If IOSTAT or IOMSG is used, the read will continue in the

[Bug fortran/45108] Namelist read: Not aborted when reading from STDIN

2010-08-17 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2010-08-17 07:54 --- (In reply to comment #4) > There was some history regarding legacy codes as the reason why this does not > error out. ie looping back and trying again was a feature. I think I may put > this behind -std=legacy. It d

[Bug fortran/45108] Namelist read: Not aborted when reading from STDIN

2010-08-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2010-08-17 03:18 --- There was some history regarding legacy codes as the reason why this does not error out. ie looping back and trying again was a feature. I think I may put this behind -std=legacy. It does seem odd the way we are

[Bug fortran/45108] Namelist read: Not aborted when reading from STDIN

2010-07-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2010-07-29 00:59 --- I will have a look. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added As

[Bug fortran/45108] Namelist read: Not aborted when reading from STDIN

2010-07-28 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2010-07-28 15:07 --- See also: http://gcc.gnu.org/onlinedocs/gfortran/Extensions-to-namelist.html I understand the support of ? and =?, but why can't one give a proper error is one returns? If one starts a dialog with ? / =?, one stays i

[Bug fortran/45108] Namelist read: Not aborted when reading from STDIN

2010-07-28 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2010-07-28 15:01 --- That seemingly goes back to implementing support for: +/* If the namelist read is from stdin, output the current state of the + namelist to stdout. This is used to implement the non-standard query + features, ?