Warp wrote:
> the foo(int) function will be called (and the compiler might give you a
> warning about this if it's smart enough).

Ah! OK. I wondered why C++ had bothered to change this, but now it makes 
sense, yes.

Actually, many times I've seen NULL defined as
   #define NULL ((void*)0)
I'm not sure which (if either) such a thing would match in your C++ example.

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message