public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/114304] [13/14 Regression] libgfortran I/O – bogus "Semicolon not allowed as separator with DECIMAL='point'"
Date: Thu, 14 Mar 2024 15:56:23 +0000	[thread overview]
Message-ID: <bug-114304-4-b2AUWPHpbc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114304-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114304

--- Comment #20 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Some additional information from the 2023 standard.

13.10.3.1List-directed input forms

8 If the next effective item is default, ASCII, or ISO 10646 character and
    • the character sequence does not contain value separators,
    • the character sequence does not cross a record boundary,
    • the first nonblank character is not a quotation mark or an apostrophe,
    • the leading characters are not digits followed by an asterisk, and
    • the character sequence contains at least one character,

  the delimiting apostrophes or quotation marks are not required. If the
delimiters are
  omitted, the character sequence is terminated by the first blank, comma (if
the decimal
  edit mode is POINT), semicolon (if the decimal edit mode is COMMA), slash, or
end of
  record; in this case apostrophes and quotation marks within the datum are not
to be
  doubled.

---------------------------------------------------

I am still digesting this and should have something sorted out in the next day
or so.

  parent reply	other threads:[~2024-03-14 15:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 11:40 [Bug libfortran/114304] New: [14 Regression] Rejects lapack test rguenth at gcc dot gnu.org
2024-03-11 11:42 ` [Bug libfortran/114304] " rguenth at gcc dot gnu.org
2024-03-11 11:52 ` rguenth at gcc dot gnu.org
2024-03-11 12:26 ` burnus at gcc dot gnu.org
2024-03-11 12:31 ` burnus at gcc dot gnu.org
2024-03-11 12:51 ` [Bug libfortran/114304] [14 Regression] libgfortran I/O – bogus "Semicolon not allowed as separator with DECIMAL='point'" burnus at gcc dot gnu.org
2024-03-11 16:41 ` burnus at gcc dot gnu.org
2024-03-11 17:27 ` [Bug libfortran/114304] [13/14 " jvdelisle at gcc dot gnu.org
2024-03-11 18:18 ` jvdelisle at gcc dot gnu.org
2024-03-11 19:03 ` jvdelisle at gcc dot gnu.org
2024-03-11 19:13 ` rguenther at suse dot de
2024-03-11 21:12 ` jvdelisle at gcc dot gnu.org
2024-03-11 22:24 ` cvs-commit at gcc dot gnu.org
2024-03-11 22:45 ` cvs-commit at gcc dot gnu.org
2024-03-12  8:52 ` burnus at gcc dot gnu.org
2024-03-12 16:42 ` jvdelisle at gcc dot gnu.org
2024-03-13 13:39 ` [Bug libfortran/114304] " law at gcc dot gnu.org
2024-03-13 19:32 ` jvdelisle at gcc dot gnu.org
2024-03-14  3:02 ` law at gcc dot gnu.org
2024-03-14  9:26 ` [Bug libfortran/114304] [13/14 Regression] " burnus at gcc dot gnu.org
2024-03-14 15:56 ` jvdelisle at gcc dot gnu.org [this message]
2024-03-15 15:00 ` law at gcc dot gnu.org
2024-03-15 23:51 ` jvdelisle at gcc dot gnu.org
2024-04-06 13:56 ` cvs-commit at gcc dot gnu.org
2024-04-08  6:03 ` chenglulu at loongson dot cn
2024-04-08  7:24 ` rguenth at gcc dot gnu.org
2024-04-08  7:49 ` rguenth at gcc dot gnu.org
2024-04-08  8:06 ` rguenth at gcc dot gnu.org
2024-04-08  8:09 ` rguenth at gcc dot gnu.org
2024-04-08  8:38 ` burnus at gcc dot gnu.org
2024-04-08  9:36 ` rguenther at suse dot de
2024-04-08 10:00 ` burnus at gcc dot gnu.org
2024-04-08 19:48 ` cvs-commit at gcc dot gnu.org
2024-04-08 20:07 ` jvdelisle at gcc dot gnu.org
2024-04-08 20:15 ` jvdelisle at gcc dot gnu.org
2024-04-22  4:23 ` cvs-commit at gcc dot gnu.org
2024-04-22  4:29 ` jvdelisle at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-114304-4-b2AUWPHpbc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).