From: Nevin Liber <nevin@eviloverlord.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] C++ / Kernel
Date: Thu, 23 Aug 2018 17:28:44 -0500 [thread overview]
Message-ID: <CAGg_6+PY70t3t4x2J7uapn9E1LodtGZhcqRavtM2ve89B97byg@mail.gmail.com> (raw)
In-Reply-To: <151301d43b2f$07881ed0$16985c70$@ronnatalie.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On Thu, Aug 23, 2018 at 5:17 PM <ron@ronnatalie.com> wrote:
> This union was right in the middle of the buf struct:
>
> union {
> caddr_t b_addr; /* low order core address */
> int *b_words; /* words for clearing */
> struct filsys *b_filsys; /* superblocks */
> struct dinode *b_dino; /* ilist */
> daddr_t *b_daddr; /* indirect block */
> } b_un;
> There were a number of other places that did the same thing. It's
> OFFICIALLY now in undefined behavior by the standard (though of course that
> didn't exist in the BSD days) ,
> to store in one element of the union and retrieve it via another.
It was still kinda frowned upon in K&R1: "It is the responsibility of the
programmer to keep track of what type is currently stored in a union; the
results are machine dependent if something is stored as one type and
extracted as another."
--
Nevin ":-)" Liber <mailto:nevin@eviloverlord.com> +1-847-691-1404
[-- Attachment #2: Type: text/html, Size: 1683 bytes --]
next prev parent reply other threads:[~2018-08-23 22:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 14:42 ron
2018-08-23 17:24 ` Clem Cole
2018-08-23 20:21 ` Bakul Shah
2018-08-23 22:17 ` ron
2018-08-23 22:28 ` Nevin Liber [this message]
2018-08-23 22:48 ` Clem Cole
2018-08-23 23:14 ` Steffen Nurpmeso
2018-08-24 14:13 ` Steffen Nurpmeso
2018-08-24 14:32 ` ron
2018-08-24 18:15 ` Steffen Nurpmeso
2018-08-26 16:34 ` Paul Winalski
2018-08-27 16:31 ` Steffen Nurpmeso
2018-08-24 1:41 ` Bakul Shah
2018-08-24 10:41 ` Pete Turnbull
2018-08-24 12:17 ` ron
2018-08-24 18:36 ` Bakul Shah
2018-08-24 18:38 ` ron
2018-08-24 1:58 ` Dan Cross
2018-08-24 3:04 ` Clem cole
2018-08-24 14:01 ` Dan Cross
2018-08-24 13:22 ` Derek Fawcus
2018-08-24 16:59 ` Steffen Nurpmeso
2018-08-23 23:29 Noel Chiappa
2018-08-23 23:42 ` ron
2018-08-24 0:30 ` Clem Cole
2018-08-24 2:05 ` Bakul Shah
2018-08-24 12:21 ` ron
2018-08-24 1:27 Noel Chiappa
2018-08-24 2:52 ` Clem cole
2018-08-24 7:30 Paul Ruizendaal
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=CAGg_6+PY70t3t4x2J7uapn9E1LodtGZhcqRavtM2ve89B97byg@mail.gmail.com \
--to=nevin@eviloverlord.com \
--cc=tuhs@minnie.tuhs.org \
/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 NNTP newsgroup(s).