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 16:39:00 -0000 [thread overview]
Message-ID: <20021005205611.277A9F2CAF@nile.gnat.com> (raw)
>>Yep, this is definitely true and might by worth stressing.
I always thought that this was a clever way of dealing with aliasing. Very
precisely defined, and you could in fact add run time checks for this if you
wanted.
next reply other threads:[~2002-10-05 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 16:39 Robert Dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-05 14:21 Robert Dewar
2002-10-05 15:00 ` Toon Moene
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=20021005205611.277A9F2CAF@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).