{ASSERT|EXPECT}_[NOT_]NULL(expr) about googletest HOT 2 CLOSED

EXPECT_EQ(NULL, baz.foo()) is supposed to work.  Which platform/compiler are 
you using?

Thanks again for your contribution.  The next time could you discuss the plan on
[email protected] first?  The reason is to make sure you 
don't end
up wasting your time.

In this particular case, we had a discussion before and decided not to implement
ASSERT_NULL and ASSERT_NOT_NULL, as there are already options that don't involve
introducing new macros:

  ASSERT_EQ(NULL, foo);
  ASSERT_TRUE(foo != NULL);
  ASSERT_THAT(foo, NotNull());
etc.

The last one depends on our mocking framework, which will be open-sourced soon. 
 Thanks.

In the end, it wasn't a waste of my time -- it's something that we're going to 
end up
using. We'll end up pulling it into an extra header that we use, instead of in
gtest/gtest.h, but ASSERT_NULL and ASSERT_NOT_NULL seemed better for us. Plus, I
wasn't trying to do NULL, but 0 (e.g., ASSERT_NE(0, baz.foo())) since the C++ 
spec
indicates that NULL as (void*)0 (the C definition) isn't correct.

I encountered this problem with VS2005.