From: Mikael Morin <mikael.morin@sfr.fr>
To: fortran@gcc.gnu.org
Cc: Janus Weil <janus@gcc.gnu.org>,
Thomas Koenig <tkoenig@netcologne.de>,
"gcc-patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran, OOP] PR 49638: [OOP] length parameter is ignored when overriding type bound character functions with constant length.
Date: Sat, 06 Aug 2011 18:27:00 -0000 [thread overview]
Message-ID: <201108061946.35514.mikael.morin@sfr.fr> (raw)
In-Reply-To: <CAKwh3qgDCq80JOpoMf9McThP7RiE_CnaaPPbMB367sKKkYPkag@mail.gmail.com>
On Saturday 06 August 2011 19:10:09 Janus Weil wrote:
> Now, if Thomas says it's fine for the other cases, too, then it seems
> we can really get away with a much simpler patch. Hope we're not
> missing anything, though ...
>
What about this case: two module variables from two different modules?
module world1
implicit none
integer :: n
type :: t1
contains
procedure, nopass :: string => w1_string
end type
contains
function w1_string (m)
integer, intent(in) :: m
character(n) :: w1_string
w1_string = "world"
end function
end module world1
module world2
use world1, only : t1
implicit none
integer :: n
type, extends(t1) :: t2
contains
procedure, nopass :: string => w2_string
end type
contains
function w2_string (m)
integer, intent(in) :: m
character(n) :: w2_string
w2_string = "world2"
end function
end module world2
next prev parent reply other threads:[~2011-08-06 17:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 21:42 Janus Weil
2011-08-05 17:26 ` Mikael Morin
2011-08-05 17:35 ` Janus Weil
2011-08-05 18:16 ` Mikael Morin
2011-08-05 21:23 ` Thomas Koenig
2011-08-05 22:06 ` Mikael Morin
2011-08-06 14:27 ` Janus Weil
2011-08-06 16:07 ` Thomas Koenig
2011-08-06 16:17 ` Mikael Morin
2011-08-06 16:24 ` Janus Weil
2011-08-06 16:59 ` Mikael Morin
2011-08-06 18:42 ` Steve Kargl
2011-08-06 16:45 ` Janus Weil
2011-08-06 16:54 ` Thomas Koenig
2011-08-06 17:10 ` Janus Weil
2011-08-06 17:40 ` Janus Weil
2011-08-06 18:27 ` Mikael Morin [this message]
2011-08-06 18:37 ` Janus Weil
2011-08-06 20:32 ` Thomas Koenig
2011-08-06 21:11 ` Janus Weil
2011-08-06 21:40 ` Thomas Koenig
2011-08-06 21:59 ` Janus Weil
2011-08-06 23:14 ` Thomas Koenig
2011-08-07 2:11 ` Janus Weil
2011-08-07 3:39 ` Mikael Morin
2011-08-07 10:57 ` Thomas Koenig
2011-08-07 11:00 ` Janus Weil
2011-08-07 11:24 ` Janus Weil
2011-08-07 12:39 ` Thomas Koenig
2011-08-07 18:49 ` Janus Weil
2011-08-07 20:08 ` Janus Weil
2011-08-07 20:31 ` Thomas Koenig
2011-08-07 23:30 ` Janus Weil
2011-08-13 16:30 ` Janus Weil
2011-08-19 12:30 ` Janus Weil
2011-08-19 12:48 ` Mikael Morin
2011-08-19 13:37 ` Tobias Burnus
2011-08-20 6:13 ` Janus Weil
2011-08-20 7:25 ` Mikael Morin
2011-08-20 21:03 ` Janus Weil
2011-08-20 21:31 ` Mikael Morin
2011-08-21 12:04 ` Thomas Koenig
2011-08-06 16:46 ` Janus Weil
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=201108061946.35514.mikael.morin@sfr.fr \
--to=mikael.morin@sfr.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=janus@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).