From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] go forth and ulong no more!
Date: Thu, 22 Nov 2012 11:45:44 +0000 [thread overview]
Message-ID: <CAOw7k5jfp2Rcq575kzhtC0R_0yzwR_=KqgY9a7dx8D8rci_9+Q@mail.gmail.com> (raw)
In-Reply-To: <ed9454dde8d6ea418f09082ca95ce43e@hamnavoe.com>
It was in v6 (and a nasty bug):
/*
* sizeof gets turned into a number here.
* Bug: sizeof(structure-member-array) is 2 because
* the array has been turned into a ptr already.
*/
if (op==SIZEOF) {
t1 = length(p1);
p1->op = CON;
p1->type = INT;
p1->dimp = 0;
p1->value = t1;
*cp++ = p1;
return;
}
but in v7 (without the bug):
/*
* sizeof gets turned into a number here.
*/
if (op==SIZEOF) {
t1 = cblock(length(p1));
t1->type = UNSIGN;
*cp++ = t1;
return;
}
It's not surprising, since "unsigned" didn't originally exist (use "char*"!)
On 22 November 2012 11:36, Richard Miller <9fans@hamnavoe.com> wrote:
>> New C programmers are often confused by
>> size_t being unsigned (even experienced ones at times)
>
> Especially experienced ones. My 1978 copy of K&R says
>
> "The expression sizeof(object) yields an integer equal to the
> size of the specified object."
>
> Not "unsigned integer". Old habits die hard.
>
>
next prev parent reply other threads:[~2012-11-22 11:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 11:36 Richard Miller
2012-11-22 11:45 ` Charles Forsyth [this message]
2012-11-22 11:54 ` Steve Simon
2012-11-22 11:59 ` Charles Forsyth
-- strict thread matches above, loose matches on Subject: below --
2012-11-20 21:49 erik quanstrom
2012-11-22 0:18 ` Federico G. Benavento
2012-11-22 1:21 ` erik quanstrom
2012-11-22 1:35 ` Bruce Ellis
2012-11-22 2:08 ` Dan Cross
2012-11-22 2:15 ` Bruce Ellis
2012-11-22 2:33 ` Charles Forsyth
2012-11-22 2:35 ` Charles Forsyth
2012-11-22 3:44 ` Bruce Ellis
2012-11-22 8:56 ` Charles Forsyth
2012-11-22 9:02 ` Charles Forsyth
2012-11-22 10:21 ` erik quanstrom
2012-11-22 11:00 ` Richard Miller
2012-11-22 11:11 ` Charles Forsyth
2012-11-22 11:13 ` Charles Forsyth
2012-11-22 11:32 ` Richard Miller
2012-11-22 11:38 ` Charles Forsyth
2012-11-22 11:49 ` erik quanstrom
2012-11-22 13:26 ` Richard Miller
2012-11-22 14:05 ` Charles Forsyth
2012-11-22 14:53 ` erik quanstrom
2012-11-22 11:50 ` erik quanstrom
2012-11-22 11:10 ` Richard Miller
2012-11-22 11:13 ` Charles Forsyth
2012-11-22 11:32 ` Charles Forsyth
2012-11-22 11:33 ` Charles Forsyth
2012-11-22 10:31 ` Charles Forsyth
2012-11-22 12:39 ` Anthony Martin
2012-11-22 12:48 ` Charles Forsyth
2012-11-22 12:50 ` Charles Forsyth
2012-11-22 12:54 ` Anthony Martin
2012-11-22 13:08 ` Charles Forsyth
2012-11-22 9:59 ` Charles Forsyth
2012-11-22 9:38 ` Charles Forsyth
2012-11-22 9:40 ` Charles Forsyth
2012-11-22 18:18 ` Federico G. Benavento
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='CAOw7k5jfp2Rcq575kzhtC0R_0yzwR_=KqgY9a7dx8D8rci_9+Q@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).