public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bdsatish at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44929] [OOP] Parsing error of  derived type name starting with 'REAL'
Date: Tue, 13 Jul 2010 17:31:00 -0000	[thread overview]
Message-ID: <20100713173059.8620.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44929-19354@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from bdsatish at gmail dot com  2010-07-13 17:30 -------
Reported by Satish at http://gcc.gnu.org/ml/fortran/2010-07/msg00152.html

Simplified testcase by Janus Weil:

type :: real_type
end type
class(real_type), allocatable :: obj
allocate(real_type :: obj)
end

This is a simple parsing bug, triggered by the fact that
type name starts with "real", which is being confused with the
intrinsic type REAL. 


-- 

bdsatish at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bdsatish at gmail dot com,
                   |                            |janus at gcc dot gnu dot org
            Summary|[OOP] Intrinsic type        |[OOP] Parsing error of
                   |                            |derived type name starting
                   |                            |with 'REAL'


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


  reply	other threads:[~2010-07-13 17:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13 17:26 [Bug fortran/44929] New: [OOP] Intrinsic type bdsatish at gmail dot com
2010-07-13 17:31 ` bdsatish at gmail dot com [this message]
2010-07-13 17:42 ` [Bug fortran/44929] [OOP] Parsing error of derived type name starting with 'REAL' burnus at gcc dot gnu dot org
2010-07-13 17:48 ` burnus at gcc dot gnu dot org
2010-07-13 20:06 ` jvdelisle at gcc dot gnu dot org
2010-07-13 20:36 ` kargl at gcc dot gnu dot org
2010-07-13 20:41 ` kargl at gcc dot gnu dot org
2010-07-13 21:01 ` kargl at gcc dot gnu dot org
2010-07-13 22:08 ` burnus at gcc dot gnu dot org
2010-07-13 22:20 ` kargl at gcc dot gnu dot org
2010-07-20  4:02 ` kargl at gcc dot gnu dot org
2010-07-20  5:39 ` kargl at gcc dot gnu dot org
2010-07-20  5:40 ` kargl at gcc dot gnu dot org
2010-07-21 22:35 ` kargl at gcc dot gnu dot org
2010-07-21 22:48 ` kargl at gcc dot gnu dot org
2010-07-21 22:49 ` kargl at gcc dot gnu dot org
2010-07-22 20:02 ` kargl at gcc dot gnu dot org
2010-07-22 20:03 ` kargl at gcc dot gnu dot org
2010-07-30 16:25 ` janus at gcc dot gnu dot org
2010-07-30 17:50 ` janus at gcc dot gnu dot org
2010-07-30 17:55 ` janus at gcc dot gnu dot org
2010-07-31  9:35 ` rguenth at gcc dot gnu dot org
2010-08-05 13:56 ` janus at gcc dot gnu dot org
2010-08-05 13:58 ` janus 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=20100713173059.8620.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).