confusing errors

[heng]

#include<iostream>
#include<string>
using namespace std;

class A
{
public:
int x;
int y;
A(int y_){y=y_;}
};

int main()
{
A aobj;
return 0;
}

When I define an object, some data members cannot be initialized and no
appropriate default constructor is available. So, there is an error.

However, even if I add the default constructor explicitly, there are
still errors in the following code.

#include<iostream>
#include<string>
using namespace std;

class A
{
public:
int x;
int y;
A();
A(int y_){y=y_;}
};

int main()
{
A aobj;
return 0;
}

Why?

[Victor Bazarov]

heng wrote:

#include<iostream>
#include<string>
using namespace std;

class A
{
public:
int x;
int y;
A(int y_){y=y_;}

Prefer initialisation over assignment. See FAQ.

};

int main()
{
A aobj;
return 0;
}

When I define an object, some data members cannot be initialized and
no appropriate default constructor is available. So, there is an
error.

However, even if I add the default constructor explicitly, there are
still errors in the following code.

#include<iostream>
#include<string>
using namespace std;

class A
{
public:
int x;
int y;
A();
A(int y_){y=y_;}
};

int main()
{
A aobj;
return 0;
}

Why?

*What* errors?

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

[Noah Roberts]

heng wrote:

#include<iostream>
#include<string>
using namespace std;

class A
{
public:
int x;
int y;
A(int y_){y=y_;}
};

int main()
{
A aobj;
return 0;
}

When I define an object, some data members cannot be initialized and no
appropriate default constructor is available. So, there is an error.

Yes, that code will fail because there is no default constructor yet
you are attempting to use one.

>
However, even if I add the default constructor explicitly, there are
still errors in the following code.

#include<iostream>
#include<string>
using namespace std;

class A
{
public:
int x;
int y;
A();
A(int y_){y=y_;}
};

int main()
{
A aobj;
return 0;
}

Why?

This one will fail to link because there is no definition for your
default constructor.

[heng]

>

This one will fail to link because there is no definition for your
default constructor.

Do I need to define my default constructor? I think the default
constructor is always as follows:

class Foo
{
public:
Foo(); //default constructor
}

[Victor Bazarov]

heng wrote:

>This one will fail to link because there is no definition for your
default constructor.

Do I need to define my default constructor? I think the default
constructor is always as follows:

class Foo
{
public:
Foo(); //default constructor
}

No. The default constructor is the one that *can be called* without
any arguments, not the one that doesn't have any arguments. Think
default argument values:

class Foo
{
public:
Foo(int a = 42); // defautl constructor
};

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

[Noah Roberts]

heng wrote:

This one will fail to link because there is no definition for your
default constructor.

Do I need to define my default constructor? I think the default
constructor is always as follows:

class Foo
{
public:
Foo(); //default constructor
}

That is a declaration, not a definition. There is an important
distinction. All that does is say Foo() exists...but if it isn't
defined somewhere then it doesn't actually exist.

The original code caused the default constructor to not be created by
creating a custom one. In other words,

class X {};

has a default constructor while,

class Y { Y(int x) {} };

does not.

With,

class Y {
Y(int x) {}
Y();
};

The compiler will hapily compile any code that uses the default
constructor for Y assuming it will find it somewhere later and be able
to link to it. If there is no

Y::Y() {}

in your code anywhere (certainly not in what you posted) then of course
it never finds it.

[heng]

Noah Roberts wrote:

>
class Y {
Y(int x) {}
Y();
};

So, in your code, the default constructor of Y is declared, but not
defined, hence it cannot be used by the compiler.

Right?

[Erik Wikström]

On 2006-12-04 18:00, heng wrote:

Noah Roberts wrote:

>>
class Y {
Y(int x) {}
Y();
};

So, in your code, the default constructor of Y is declared, but not
defined, hence it cannot be used by the compiler.

Actually the compiler will be happy but the linker won't.

--
Erik Wikström

[heng]

Erik Wikström wrote:

On 2006-12-04 18:00, heng wrote:

Noah Roberts wrote:

>
class Y {
Y(int x) {}
Y();
};

So, in your code, the default constructor of Y is declared, but not
defined, hence it cannot be used by the compiler.

Actually the compiler will be happy but the linker won't.

--
Erik Wikström

Thanks a lot. What's the role of the linker?

[Erik Wikström]

On 2006-12-04 19:20, heng wrote:

Erik Wikström wrote:

>On 2006-12-04 18:00, heng wrote:

Noah Roberts wrote:

class Y {
Y(int x) {}
Y();
};

So, in your code, the default constructor of Y is declared, but not
defined, hence it cannot be used by the compiler.

Actually the compiler will be happy but the linker won't.

--
Erik Wikström

Thanks a lot. What's the role of the linker?

The compiler takes each .cpp-file and compiles it (before that the
pre-processor has expanded all your #includes into the file *) which
gives you an object-file, one for each .cpp-file. The linker than takes
all the object-files and puts them together into an executable. This is
good since when you change one .cpp-file you don't have to recompile all
the others, just the change one and then re-link it all.

* What the pre-processor does is to replace each #include-line with the
content of the file given, which can create quite large files. This
large file is a compilation-unit, which is what the compiler operates on.

--
Erik Wikström

[heng]

Thanks a lot.

Erik Wikström wrote:

On 2006-12-04 19:20, heng wrote:

Erik Wikström wrote:

On 2006-12-04 18:00, heng wrote:
Noah Roberts wrote:

class Y {
Y(int x) {}
Y();
};

So, in your code, the default constructor of Y is declared, but not
defined, hence it cannot be used by the compiler.

Actually the compiler will be happy but the linker won't.

--
Erik Wikström

Thanks a lot. What's the role of the linker?

The compiler takes each .cpp-file and compiles it (before that the
pre-processor has expanded all your #includes into the file *) which
gives you an object-file, one for each .cpp-file. The linker than takes
all the object-files and puts them together into an executable. This is
good since when you change one .cpp-file you don't have to recompile all
the others, just the change one and then re-link it all.

* What the pre-processor does is to replace each #include-line with the
content of the file given, which can create quite large files. This
large file is a compilation-unit, which is what the compiler operates on.

--
Erik Wikström