public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55901] [OOP] type is (character(len=*)) misinterpreted as array
Date: Tue, 09 Dec 2014 09:02:00 -0000 [thread overview]
Message-ID: <bug-55901-4-UVGOeRDurp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55901-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55901
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org,
| |vehre at gmx dot de
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Harald Anlauf from comment #6)
> Any news on this one?
Dear Harald,
I'll take a look at it tonight. Andre is working on a patch that will allow the
likes of oo.f90 to work correctly with characters. This bug gets in the way and
so I will see what can be done :-) It should be trivial.....
Cheers
Paul
next prev parent reply other threads:[~2014-12-09 9:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 19:37 [Bug fortran/55901] New: " anlauf at gmx dot de
2013-04-08 17:13 ` [Bug fortran/55901] " pdande1 at dow dot com
2013-04-08 17:29 ` anlauf at gmx dot de
2013-04-08 17:41 ` pdande1 at dow dot com
2013-04-08 18:16 ` anlauf at gmx dot de
2013-09-18 11:51 ` janus at gcc dot gnu.org
2014-12-04 21:13 ` anlauf at gmx dot de
2014-12-09 9:02 ` pault at gcc dot gnu.org [this message]
2014-12-14 21:16 ` paul.richard.thomas at gmail dot com
2014-12-14 21:18 ` paul.richard.thomas at gmail dot com
2015-01-06 19:50 ` anlauf at gmx dot de
2015-01-07 13:16 ` paul.richard.thomas at gmail dot com
2015-01-07 16:09 ` vehre at gmx dot de
2015-01-18 12:22 ` pault at gcc dot gnu.org
2015-03-24 12:19 ` vehre at gcc dot gnu.org
2015-03-25 9:59 ` vehre 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=bug-55901-4-UVGOeRDurp@http.gcc.gnu.org/bugzilla/ \
--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).