From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <b9031f8268bf8e22bc0d106bc1a9ce13@quanstro.net>
To: 9fans@9fans.net
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 28 Apr 2008 10:12:35 -0400
In-Reply-To: <006cc24d595f7b43910034f84f6c8287@terzarima.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] ftpfs ahould not expose "." and ".." directories
Topicbox-Message-UUID: 9a39aac8-ead3-11e9-9d60-3106f5b1d025

>> 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