From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Damian Rouson <damian@sourceryinstitute.org>
Cc: Mikael Morin <mikael.morin@sfr.fr>,
"Bader, Reinhold" <Reinhold.Bader@lrz.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"salvatore.filippone@uniroma2.it"
<salvatore.filippone@uniroma2.it>
Subject: Re: [Bug fortran/52846] [F2008] Support submodules - part 3/3
Date: Fri, 24 Jul 2015 12:10:00 -0000 [thread overview]
Message-ID: <CAGkQGiJfLWasGbVOFgbyxviuzZk9RmQdJ=4tAANQ1NSdeNXsVA@mail.gmail.com> (raw)
In-Reply-To: <00370BD5-507A-42BF-9D59-E868BBAD3C94@sourceryinstitute.org>
Dear All,
In the words of Jean-Luc Picard, "I will make it so.... "
Paul
On 24 July 2015 at 10:08, Damian Rouson <damian@sourceryinstitute.org> wrote:
> I love this idea and had similar thoughts as well.
>
> :D
>
> Sent from my iPhone
>
>> On Jul 24, 2015, at 1:06 AM, Paul Richard Thomas <paul.richard.thomas@gmail.com> wrote:
>>
>> Dear Mikael,
>>
>> It had crossed my mind also that a .mod and a .smod file could be
>> written. Normally, the .smod files are produced by the submodules
>> themselves, so that their descendants can pick up the symbols that
>> they generate. There is no reason at all why this could not be
>> implemented; early on in the development I did just this, although I
>> think that it would now be easier to modify this patch.
>>
>> One huge advantage of proceeding in this way is that any resulting
>> library can be distributed with the .mod file alone so that the
>> private entities are never exposed. The penalty is that a second file
>> is output.
>>
>> With best regards
>>
>> Paul
>>
>>> On 23 July 2015 at 17:42, Mikael Morin <mikael.morin@sfr.fr> wrote:
>>> Hello Paul,
>>>
>>> Le 23/07/2015 09:46, Paul Richard Thomas a écrit :
>>>>
>>>> Since all the private entities in a module have to be transmitted to
>>>> their descendant submodules, whilst keeping them hidden from normal
>>>> use statements, I have chosen to write the module file as usual and
>>>> add a second part that contains the private entities. This latter is
>>>> only read when processing submodule statements.
>>> why not write them to the/a .smod file? It was its primary purpose, wasn't
>>> it?
>>> [Sorry, I followed the submodule stuff very remotely].
>>>
>>> It's probably bad practice to put private entities in module files, at least
>>> now that submodules are supported. Nevertheless with your change,
>>> modifications made to private entities produce recompilation cascades, even
>>> though the public interfaces are left unchanged.
>>>
>>> Mikael
>>
>>
>>
>> --
>> Outside of a dog, a book is a man's best friend. Inside of a dog it's
>> too dark to read.
>>
>> Groucho Marx
--
Outside of a dog, a book is a man's best friend. Inside of a dog it's
too dark to read.
Groucho Marx
next prev parent reply other threads:[~2015-07-24 12:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 8:37 Paul Richard Thomas
2015-07-23 8:42 ` Damian Rouson
2015-07-23 8:46 ` Paul Richard Thomas
2015-07-23 16:35 ` Mikael Morin
2015-07-24 8:08 ` Paul Richard Thomas
2015-07-24 8:09 ` Damian Rouson
2015-07-24 12:10 ` Paul Richard Thomas [this message]
2015-07-29 15:32 ` Paul Richard Thomas
2015-07-29 15:36 ` Marek Polacek
2015-07-29 16:15 ` FX
2015-07-29 16:25 ` Marek Polacek
2015-07-29 16:45 ` Paul Richard Thomas
2015-08-03 10:45 ` Mikael Morin
2015-08-03 12:36 ` Paul Richard Thomas
2015-08-03 15:40 ` Mikael Morin
2015-08-04 9:40 ` Paul Richard Thomas
2015-08-05 12:09 ` Paul Richard Thomas
2015-08-10 18:09 ` Toon Moene
2015-08-10 18:57 ` AW: " Bader, Reinhold
2015-08-11 10:28 ` Paul Richard Thomas
2015-08-11 11:17 ` AW: " Bader, Reinhold
2015-08-11 11:36 ` Paul Richard Thomas
2015-07-23 12:20 Salvatore Filippone
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='CAGkQGiJfLWasGbVOFgbyxviuzZk9RmQdJ=4tAANQ1NSdeNXsVA@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=Reinhold.Bader@lrz.de \
--cc=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikael.morin@sfr.fr \
--cc=salvatore.filippone@uniroma2.it \
/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).