From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] nil, and the danger of zero
Date: Fri, 4 Apr 2014 01:48:34 -0400 [thread overview]
Message-ID: <184dcad1c1fd8efc07e670097571cf82@ladd.quanstro.net> (raw)
In-Reply-To: <20140404054024.GT3145@iota.offblast.org>
> (void *)0 is certainly not the same as 0.
> depending on architecture and compiler, of course.
it's not the compiler, it's the type model, which if anything
is tied to the hardware. you just won't have this sort of
problem on a 32-bit machine. which is why this code has
been just like that in plan 9 for 15 or more years.
- erik
next prev parent reply other threads:[~2014-04-04 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 5:35 erik quanstrom
2014-04-04 5:40 ` Nick Owens
2014-04-04 5:48 ` erik quanstrom [this message]
2014-04-04 5:08 ` lucio
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=184dcad1c1fd8efc07e670097571cf82@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).