unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Raul Laasner <raullaasner@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 19809@debbugs.gnu.org
Subject: bug#19809: 24.4; f90-beginning-of-subprogram wrong behavior with string continuation
Date: Wed, 11 Feb 2015 21:33:37 +0200	[thread overview]
Message-ID: <CADOJ32BFNsSJDV3229-bN242KVt+g7hZjptUNx6oVR0eE4b0ng@mail.gmail.com> (raw)
In-Reply-To: <alk2zo6zal.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

I stand corrected. Indeed, what I said before only applies to a
noncharacter context.

On Wed, Feb 11, 2015 at 9:09 PM, Glenn Morris <rgm@gnu.org> wrote:

> Raul Laasner wrote:
>
> > I don't think the standard requires the second '&', although it is
> > recommended.
>
> By my reading, it does require it.
> Quoting from FCD 1539-1:
>
>     3.3.2.4 Free form statement continuation:
>
>     [...]
>
>     If a character context is to be continued, an "&" shall be the last
>     nonblank character on the line and shall not be followed by commentary.
>     There shall be a later line that is not a comment; an "&" shall be the
>     first nonblank character on the next such line and the statement
>     continues with the next character following that "&".
>
> Maybe it has changed in newer version of the standard.
>



-- 
Raul Laasner
Institute of Physics
University of Tartu
Ravila 14c, 50411, Estonia
e-mail: raullaasner@gmail.com
cell: (+372)5182268

[-- Attachment #2: Type: text/html, Size: 1560 bytes --]

  reply	other threads:[~2015-02-11 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 20:25 bug#19809: 24.4; f90-beginning-of-subprogram wrong behavior with string continuation Raul Laasner
2015-02-11  1:27 ` Glenn Morris
2015-02-11  9:53   ` Raul Laasner
2015-02-11 19:09     ` Glenn Morris
2015-02-11 19:33       ` Raul Laasner [this message]
2015-02-24  7:18         ` Glenn Morris

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=CADOJ32BFNsSJDV3229-bN242KVt+g7hZjptUNx6oVR0eE4b0ng@mail.gmail.com \
    --to=raullaasner@gmail.com \
    --cc=19809@debbugs.gnu.org \
    --cc=rgm@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).