public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19101] missing & in character continuation not caught
Date: Wed, 15 Mar 2006 07:03:00 -0000	[thread overview]
Message-ID: <20060315070328.22060.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19101-9515@http.gcc.gnu.org/bugzilla/>



------- 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  <jvdelisle@gcc.gnu.org>

        PR fortran/19101
        * gfortran.h: Add warn_ampersand.
        * invoke.texi: Add documentation for new option.
        * lang.opt: Add Wampersand.
        * options.c (gfc_init_options): Initialize warn_ampersand.
        (gfc_post_options): Set the warn if pedantic.
        (set_Wall): Set warn_ampersand.
        (gfc_handle_option: Add Wampersand for itself, -std=f95, and
-std=f2003.
        * scanner.c (gfc_next_char_literal): Add test for missing '&' in
        continued character constant and give warning if missing.

Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/gfortran.h
    trunk/gcc/fortran/invoke.texi
    trunk/gcc/fortran/lang.opt
    trunk/gcc/fortran/options.c
    trunk/gcc/fortran/scanner.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19101


  parent reply	other threads:[~2006-03-15  7:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19101-9515@http.gcc.gnu.org/bugzilla/>
2006-02-22  2:01 ` jvdelisle at gcc dot gnu dot org
2006-03-06  6:23 ` jvdelisle at gcc dot gnu dot org
2006-03-08  7:35 ` patchapp at dberlin dot org
2006-03-09  6:08 ` jvdelisle at gcc dot gnu dot org
2006-03-12  5:15 ` patchapp at dberlin dot org
2006-03-15  7:03 ` jvdelisle at gcc dot gnu dot org [this message]
2006-03-15  7:08 ` jvdelisle at gcc dot gnu dot org
2006-04-07 21:08 ` jvdelisle at gcc dot gnu dot org
2006-04-07 21:12 ` jvdelisle at gcc dot gnu dot org
2006-04-07 21:20 ` jvdelisle at gcc dot gnu dot org
2004-12-21  9:42 [Bug fortran/19101] New: " Thomas dot Koenig at online dot de
2004-12-21 18:49 ` [Bug fortran/19101] " pinskia at gcc dot gnu dot org
2004-12-25  0:41 ` eedelman at acclab dot helsinki dot fi
2004-12-25  9:31 ` Thomas dot Koenig at online dot de
2004-12-27 21:41 ` tobi at gcc dot gnu dot org
2004-12-27 21:47 ` tobi at gcc dot gnu dot org
2004-12-28 19:19 ` tobi at gcc dot gnu dot 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=20060315070328.22060.qmail@sourceware.org \
    --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).