n00b question regarding classes

I wanna build a Class called "Building" and each building object
has a number of rooms(int), floors(int), floor area(int) and a heating type(char "e" or "o")
either Electric or Oil. Initial Values should be 0(zero) and "e"

tell me if i got this right or not

Code:

#ifndef BUILDING_H
#define BUILDING_H

class Building
{

public:												// Electric = "E" Oil = "O"
	Specs(int = 0, int = 0, int = 0, char = "e");	// Heating type
	void setRooms(int);								// set rooms
	void setFloors(int);							// set Floors
	void setArea(int);								// set Area
	void heatingType(char);							// set Heating Type

	// get functions
	int getRooms();									// return Rooms
	int getFloors();								// return Floors
	int getArea();									// return Area
	char heatingType();								// return Heating Type
	
private:
	int Rooms;
	int Floor;
	int Area;
	char Heat;

}

close...

Code:

void Specs(int R=0, int F=0, int A=0, char H='e');

then don't forget to actually assign those values when you define the constructor...

Personally I would organize things a bit differently. A building has floors so I would make my Building class contain a vector of Floor objects. A Floor contains rooms so I would maybe make a Floor class contain a vector of Room objects, etc... (depends on how detailed/complex you want to get)

Code:

class Building
{

public:
    // This looks like a constructor, in that it does not have a return type...
    // But it is not named the same as the class name, error?
    // Plus what major_small already said...
    Specs(int = 0, int = 0, int = 0, char = "e");  

}; // Missing semicolon

I missed that that wasn't a constructor, but hk's right... you're going to need to fix that into a constructor...

I wouldn't worry about the level of detail hk suggested though--unless you have a practical purpose for that, it may be overkill

Thanks for the help guys... i think i got it figured out....almost.... i have to admit this is the best programming forum out there... i'm sure i'll have more questions later on..