public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linuxl4 at sohu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45337] gfortran accepts pointer initialization of DT dummy arguments w/ INTENT(OUT)
Date: Fri, 20 Aug 2010 06:50:00 -0000	[thread overview]
Message-ID: <20100820065014.24721.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45337-15353@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from linuxl4 at sohu dot com  2010-08-20 06:50 -------
Error: Dummy 'x' at (1) cannot have an initializer

I think this is easy to understand, an additional short message about why it
can't have an initializer will be better.

> 
>   It helps if you already state (a) the error message and (b) what you expect
> in the first
>   description.
> 


-- 


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


  parent reply	other threads:[~2010-08-20  6:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19  9:14 [Bug fortran/45337] New: intent(out) and pointer => null() linuxl4 at sohu dot com
2010-08-19  9:14 ` [Bug fortran/45337] " linuxl4 at sohu dot com
2010-08-19  9:22 ` jv244 at cam dot ac dot uk
2010-08-19  9:22 ` linuxl4 at sohu dot com
2010-08-19  9:26 ` linuxl4 at sohu dot com
2010-08-19  9:40 ` [Bug fortran/45337] gfortran accepts pointer initialization of DT dummy arguments w/ INTENT(OUT) burnus at gcc dot gnu dot org
2010-08-19  9:47 ` burnus at gcc dot gnu dot org
2010-08-19  9:56 ` burnus at gcc dot gnu dot org
2010-08-20  6:50 ` linuxl4 at sohu dot com [this message]
2010-08-20  8:45 ` burnus at gcc dot gnu dot org
2010-08-20  8:57 ` jv244 at cam dot ac dot uk
2010-08-20 22:29 ` burnus at gcc dot gnu dot org
     [not found] <bug-45337-4@http.gcc.gnu.org/bugzilla/>
2013-03-29  9:27 ` Joost.VandeVondele at mat dot ethz.ch
2020-07-07 13:50 ` markeggleston at gcc dot gnu.org
2020-07-13 15:38 ` cvs-commit at gcc dot gnu.org
2020-07-14  7:05 ` markeggleston 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=20100820065014.24721.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).