From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ftpfs ahould not expose "." and ".." directories
Date: Mon, 28 Apr 2008 10:12:35 -0400 [thread overview]
Message-ID: <b9031f8268bf8e22bc0d106bc1a9ce13@quanstro.net> (raw)
In-Reply-To: <006cc24d595f7b43910034f84f6c8287@terzarima.net>
>> similarly, it is usually
>> if(p != nil)
>> ...
>> not
>> if(!p)
>
> ha ha. sorry i meant
> if(p == nil)
> not
> if(!p)
personal opinion here.
while i appreciate the sentiment behind nil, it breaks
down for me around the edges. zero is the one value that
can be assigned to anything. i think the c standard
thinks about zero like andy worhol thinks about coke.
you know that
pointers can be zero
and integers can be zero
your ptr can be zero, too.
a zero is a zero and
no amount of casting about
will get you a better zero.
(all things being equal, i'd rather have a coke than a zero,
but i digress....)
what it does get you is longer lines, which many folk still wrap
at 80 characters. and all things being equal, i find unwrapped
lines easier to read.
- erik
next prev parent reply other threads:[~2008-04-28 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 8:48 eekee57
2008-04-28 10:19 ` Pietro Gagliardi
2008-04-28 10:38 ` Juan Céspedes
2008-04-28 10:50 ` Charles Forsyth
2008-04-28 13:54 ` Charles Forsyth
2008-04-28 14:12 ` erik quanstrom [this message]
2008-04-29 8:32 ` eekee57
2008-04-29 10:16 ` roger peppe
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=b9031f8268bf8e22bc0d106bc1a9ce13@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).