From: Bryan Everly <bryan@bceassociates.com>
To: "Holcomb, Katherine A. (kah3f)" <kah3f@eservices.virginia.edu>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: Inheritance across modules
Date: Tue, 12 Jul 2016 18:35:00 -0000 [thread overview]
Message-ID: <09713334-dfc2-b0b3-451a-7e7cf50b4c58@bceassociates.com> (raw)
In-Reply-To: <9D538006-22B5-4837-BEBC-B494C5F3F021@eservices.virginia.edu>
Will do. Apologies.
On 07/12/16 14:25, Holcomb, Katherine A. (kah3f) wrote:
> Hi Bryan,
>
> Welcome to Fortran. The fortran@gcc.gnu.org mailing list is for technical discussions by the compiler developers and not for general questions. I’d suggest you post your question to the Google group comp.lang.fortran and you should get plenty of examples. I may have one I could find and send you separately. Is the type a class (i.e. are the procedures type bound, as we say in Fortranese)?
>
prev parent reply other threads:[~2016-07-12 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 17:49 Bryan C. Everly
2016-07-12 18:25 ` Holcomb, Katherine A. (kah3f)
2016-07-12 18:33 ` Anton Shterenlikht
2016-07-12 18:35 ` Bryan Everly [this message]
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=09713334-dfc2-b0b3-451a-7e7cf50b4c58@bceassociates.com \
--to=bryan@bceassociates.com \
--cc=fortran@gcc.gnu.org \
--cc=kah3f@eservices.virginia.edu \
/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).