NULL value

[John Ratliff]

If I need a NULL value, should I define it myself, or include a standard
header of some kind?

I've been including <cstdio> whenever I need it, but is it just as good
to do something like

#define NULL (void *)0

Thanks,

--John Ratliff

[Artie Gold]

John Ratliff wrote:

If I need a NULL value, should I define it myself, or include a standard
header of some kind?

I've been including <cstdio> whenever I need it, but is it just as good
to do something like

#define NULL (void *)0

Thanks,

--John Ratliff

You have two options:

#include <cstdlib>

or, just use 0.

HTH,
--ag

--
Artie Gold -- Austin, Texas
http://goldsays.blogspot.com (new post 8/5)
http://www.cafepress.com/goldsays
"If you have nothing to hide, you're not trying!"

[Victor Bazarov]

John Ratliff wrote:

If I need a NULL value, should I define it myself, or include a standard
header of some kind?
Usually including <cstdlib> takes care of that.
I've been including <cstdio> whenever I need it, but is it just as good
to do something like

#define NULL (void *)0

No, you mustn't do that. If you're compiling C++, you are allowed to do

#define NULL 0

but no (void*) nonsense.

V

[Alf P. Steinbach]

* John Ratliff:

If I need a NULL value, should I define it myself,
No.
or include a standard header of some kind?
You don't need to, just write

0

I've been including <cstdio> whenever I need it,
If you just need the name NULL it would be more natural to use [cstddef],
since it doesn't drag in some many other definitions.

but is it just as good to do something like

#define NULL (void *)0

It's not valid to redefine a standard macro, and besides, the definition in
C++ isn't "(void*)0", but typically just "0": §18.1/4 note 180 "Possible
definitions include 0 and 0L, but not (void*)0" (see §4.10/1 for details).

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[John Ratliff]

Alf P. Steinbach wrote:

* John Ratliff:

If I need a NULL value, should I define it myself,

No.

or include a standard header of some kind?

You don't need to, just write

0

I've been including <cstdio> whenever I need it,

If you just need the name NULL it would be more natural to use [cstddef],
since it doesn't drag in some many other definitions.

but is it just as good to do something like

#define NULL (void *)0

It's not valid to redefine a standard macro, and besides, the definition in
C++ isn't "(void*)0", but typically just "0": §18.1/4 note 180 "Possible
definitions include 0 and 0L, but not (void*)0" (see §4.10/1 for details).

Thanks. This is what I wanted to know.

--John Ratliff