From: dewar@gnat.com (Robert Dewar)
To: dewar@gnat.com, toon@moene.indiv.nluug.nl
Cc: gcc@gcc.gnu.org, nathan@codesourcery.com
Subject: Re: Type based aliasing
Date: Sat, 05 Oct 2002 14:21:00 -0000 [thread overview]
Message-ID: <20021005203332.A8670F2CAF@nile.gnat.com> (raw)
<<`Define' in Fortran-speak is to `have a value assigned to it and all of
the entities that are associated with it'.
Assignment is one way to cause problems here, but not the only one.
>>
OK, sure, I was using assignment loosely, but the statement that "Fortran
rules don't allow arguments to overlap at all" is definitely misleading,
since it is just fine for arguments to overlap providing that no definitions
occur in an aliased situation.
next reply other threads:[~2002-10-05 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 14:21 Robert Dewar [this message]
2002-10-05 15:00 ` Toon Moene
-- strict thread matches above, loose matches on Subject: below --
2002-10-05 16:39 Robert Dewar
2002-10-05 12:51 Robert Dewar
2002-10-05 13:33 ` Toon Moene
2002-10-02 14:47 Nathan Sidwell
2002-10-02 15:39 ` Michael Matz
2002-10-02 16:17 ` Michael Matz
2002-10-05 12:00 ` Toon Moene
2002-10-05 12:45 ` Nathan Sidwell
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=20021005203332.A8670F2CAF@nile.gnat.com \
--to=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=nathan@codesourcery.com \
--cc=toon@moene.indiv.nluug.nl \
/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).