Click here to Skip to main content
15,887,404 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
#include<iostream>
#include<string>
using namespace std;
class student{
	
	protected:
		string name;
	int age;
	public:
		student(){
		}
      student(string n,int a){
      	name=n;
      	age=a;
	  }	
	  void input()
	  {
	  	cin>>name>>age;
	  }
	  void display()
	  {
	  	cout<<"name:"<<name<<"\n"<<"age:"<<age<<"\n";
	  }
};
class teacher:public student
{
	string course;
	public:
		teacher():student()
		{
		}
		teacher(string n,int a,string c){
			student(n,a);
			course=c;
		}
		void input()
		{
			student::input();
			cin>>course;
		}
		void display()
		{
			student::display();
			cout<<"course:"<<course<<"\n";
		}
};
int main()
{
	student st;
	cout<<"Enter name and age of Student\n";
	st.input();
	cout<<"Student details:\n";
	st.display();
	
	teacher tr("SRI",50,"BE");
	cout<<"Teacher details:\n";
	tr.display();
	return 0;
}


What I have tried:

not getting child class name and age
Posted
Updated 3-Aug-17 23:01pm
v2

The error is in the teacher constructor accepting parameters:
teacher(string n,int a,string c) 
{
    student(n,a);
    course=c;
}
There you are creating a local student instance from the parameters but that goes out of scope when leaving the constructor letting the members unitialised.

You have to do it this way:
teacher(string n,int a,string c) : student(n,a)
{
    course=c;
}
 
Share this answer
 
Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
C#
private int Double(int value)
   {
   return value * value;
   }

Once you have an idea what might be going wrong, start using teh debugger to find out why. Put a breakpoint on your line:
C#
st.input();

and run your app. Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?

This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!

Yes, I could probably tell you what "the problem" is - but it's not difficult to do this yourself, and you will learn something really worthwhile at the same time!
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900