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 11:53:18 +0200 [thread overview]
Message-ID: <CADOJ32DAyG7CMiRq7Te8zscidmSX5GZMs=YEgs7ndvdqaby3bQ@mail.gmail.com> (raw)
In-Reply-To: <ka8ug58cg2.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
I don't think the standard requires the second '&', although it is
recommended. Moreover, GFortran permits its omission and so in practice
people sometimes write such code. In any case, I have realized that the
proposed modification leads to new problems because in principle one could
also have
subroutine foo
! &
end subroutine foo
or something as weird as
subroutine foo
; &
end subroutine foo
and it's probably not worth the effort to account for such unlikely cases.
If the function is used mainly interactively then it's immediately clear
anyway if it fails due to unusual coding style. (On a different subject, it
also fails if the subprogram ends with a bare 'end' not followed by a
keyword, also allowed by the standard.)
On Wed, Feb 11, 2015 at 3:27 AM, Glenn Morris <rgm@gnu.org> wrote:
> Raul Laasner wrote:
>
> > The functions f90-beginning-of-subprogram and f90-end-of-subprogram do
> not
> > work correctly if the source file contains lines which begin with the
> > correct keywords but in fact belong to a continued string. For instance,
> in
> > the following,
> >
> > subroutine foo()
> > print*, '&
> > end subroutine foo'
> > ! The cursor is here
> > end subroutine foo
>
> But that's not valid Fortran? Continued strings must use '&' at the
> start of the continued lines as well? Eg gfortran 4.8.2 says:
>
> Warning: Missing '&' in continued character constant at (1)
>
> Ie, you must write
>
> subroutine foo()
> print*, '&
> &end subroutine foo'
> end subroutine foo
>
> in which case there isn't a problem.
>
--
Raul Laasner
Institute of Physics
University of Tartu
Ravila 14c, 50411, Estonia
e-mail: raullaasner@gmail.com
[-- Attachment #2: Type: text/html, Size: 2526 bytes --]
next prev parent reply other threads:[~2015-02-11 9:53 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 [this message]
2015-02-11 19:09 ` Glenn Morris
2015-02-11 19:33 ` Raul Laasner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADOJ32DAyG7CMiRq7Te8zscidmSX5GZMs=YEgs7ndvdqaby3bQ@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.