Hi,

When assigning variables at initialization, is the following
allowed:
class Field;

int main(void)
{
Field * p_field(NULL);
return EXIT_SUCCESS;
}

I've switch to using MS Visual C++ 6.0 and it is giving me
errors for the assignment. However, Borland 5.2 and GNU
g++ 3.4.4 do not give any errors.

My belief is that the above is correct syntax.

Unfortunately, I'm have to change all of these and
similar instances to:
Field * p_field = NULL;
to get the code to compiler under MSVC++ 6.0

--
Thomas Matthews

C++ newsgroup welcome message:
http://www.slack.net/~shiva/welcome.txt
C++ Faq: http://www.parashift.com/c++-faq-lite
C Faq: http://www.eskimo.com/~scs/c-faq/top.html
alt.comp.lang.learn.c-c++ faq:
http://www.comeaucomputing.com/learn/faq/
Other sites:
http://www.josuttis.com -- C++ STL Library book
http://www.sgi.com/tech/stl -- Standard Template Library

Thomas Matthews wrote:
VC++ >6 permits that correct notation.

I suspect there are those who will promote constructor-notation for all
initializations. However, I can't think of a rationale besides "it's just
obviously better!"

--
Phlip
http://www.greencheese.us/ZeekLand <-- NOT a blog!!!

In article <YcARg.7723$Ij.2977@newssvr14.news.prodigy.com>,
phlipcpp@yahoo.com says...

[ ... ]
The obvious reasoning here is that constructor notation instructs the
compiler to construct the object with the value directly. Notation like:

whatever x=something;

really instructs the compiler to create a temporary object initialized
with 'something', then use whatever's copy constructor to create x, then
destroy the temporary. For built-in types, this is rarely a problem, but
for other types that take longer to create, copy and/or destroy, this is
substantially slower. Likewise, for extremely large objects, this wastes
memory creating two objects where only one is really needed.

--
Later,
Jerry.

The universe is a figment of its own imagination.

Phlip wrote :
The constructor notation can cause problems related to function declaration.

Jerry Coffin wrote:The reality is a bit better but somewhat convoluted, I am afraid.
The compiler is explicitly allowed to forgo creation of a temporary
in such case, even if the copy c-tor has side effects (see 12.8/15).
However, the copy c-tor has to be accessible *as if* copying does take
place.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask

Thomas Matthews wrote :
Then switch again to a C++ compiler.

Thomas Matthews wrote:Well, that's what you get for using an 8-year-old compiler. If you're
going to use MSVC at least use the most recent version (which is a lot
more standard-compliant BTW).

Regards,
Bart.

loufoque wrote:It compiles on VC++ 8, which is much much closer to being a C++
compiler.

Jeff