.2 alignment
requirement that objects of a particular type be located on storage boundaries with addresses that are particular multiples of a byte address
.2.3
Not present.
Good job proving >>11 wrong there, champ.
Objection! Panjo Batterson here; back from my temporary vacation.
It seems that Mr. 10's point was that, regardless of a null pointer's internal representation, it will always compare equal to 0. The examples provided by Mr. 10 hold up in The Court of C according to the sections referred by Mr. 15 in THE STANDARDS (which indeed confirm Mr. 10's supposed point), and so Mr. 11's bold claim that Mr. 10 doesn't know what he is talking about is false.
Any objections to my objection? If not, I consider this case closed. *Bangs a plastic mallet on my desk*
Name:
Anonymous2012-05-09 19:24
>>9 NULL is defined to be a null pointer constant so it's either 0 or ((void *) 0), if you convert it to a pointer type then you get a null pointer.
I believe what you're actually wondering about is answered in >>11-san's link.
>>15
Still doesn't back you up. There's a difference between NULL and an actual null pointer.
Name:
Anonymous2012-05-09 19:43
∧_∧
( ´∀`)< ぬるぽ
Name:
Anonymous2012-05-09 20:00
glad you think that way. but making a habit of fapping has been scientifically proven to be healthy and reduce certain kinds of cancer like prostate cancer. lots of ppl in my family have had prostate cancer....i wish i could fap a lot, but i take a lot of antipsychotics and antidepressants that make it a very hard thing to do. I usually can't do it without perverted Touhou material.lol << May the Flying Spaghetti Monster bless you!!! i've enjoyed arguing with ya