Explicitly calling constructor

[Kavya]

Suppose I have class MyClass. Then which will be termed as explicit
call to constructor.

MyClass( );

or

MyClass object;
object.MyClass( );

[Alf P. Steinbach]

* Kavya:

Suppose I have class MyClass. Then which will be termed as explicit
call to constructor.

MyClass( );

or

MyClass object;
object.MyClass( );

The second line of the latter isn't valid code.

The first is an example of what the standard calls an explicit
constructor call, while the first line of the second example is a
declaration with an implicit constructor call.

Used as a stand-alone expression statement (some illuminating context
would be nice!) "MyClass();" creates a temporary of MyClass type and
calls the default constructor on that temporary.

--
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?

[Osamede.Zhang]

Kavya wrote:

Suppose I have class MyClass. Then which will be termed as explicit
call to constructor.

MyClass( );

or

MyClass object;

When the object was declared,it was automatic initialized by calling
class's contructor.

object.MyClass( );

[Frederick Gotham]

Kavya:

MyClass( );

That createless a nameless object which exists until the end of the
statement. The following two snippets are equivalent:

int main()
{
int i = MyClass().GetVal();
}

int main()
{
int i;

{
MyClass nameless_object;
i = nameless_object.GetVal();
}
}

If you would like to invoke a class's constructor, you need to supply it
with a memory address at which to construct an object of the class in
question. "Placement new" is used for this:

void *const pmem = malloc(512);

MyClass *const p = ::new((void*)pmem) MyClass();

p->~MyClass();

free(pmem);

--

Frederick Gotham