Template/classes/strings

I have this relatively easy asignment for school (only thing is that "tutorials" for C++ on the internet are TOO DAMN COMPLICATED so I bearly understand a thing :|)

I get the errors

Code:

In member function `PACKAGE DATE_EXP<PACKAGE>::INSERT_DATE_EXP() [with PACKAGE = char]': 
 instantiated from here 
invalid conversion from `char' to `char*' 
initializing argument 1 of `char* gets(char*)'

because of the "gets(NAME_EXP);" thing but I need to use it to put something like "bla bla text with spaces" because string normally doesn't accept spaces

Code:

template <class PACKAGE>
class DATE_EXP{
PACKAGE NAME_EXP    ,ADRESS_EXP      ;
public:
DATE_EXP(PACKAGE first,PACKAGE second){NAME_EXP=first,ADRESS_EXP=second;}
PACKAGE INSERT_DATE_EXP ();
}; //class DATE_EXP
template <class PACKAGE>
PACKAGE DATE_EXP<PACKAGE>::INSERT_DATE_EXP            (){
gets(NAME_EXP);
gets(ADRESS_EXP);
cout<<"NAME_EXP IS "<<NAME_EXP<<"\n";
cout<<"ADRESS_EXP IS "<<ADRESS_EXP<<"\n";

main(){

char NAME_EXP_TEMP,ADRESS_EXP_TEMP;
DATE_EXP<char>EXP_TEMP(NAME_EXP_TEMP,ADRESS_EXP_TEMP);
cout<<EXP_TEMP.INSERT_DATE_EXP();


}

No using gets!

Read up on the wonderful world of iomanip.

sorry, I don't get it

you just sent me back to the place with lots of complicated "tutorials" that I don't understand

could you at least point out which one of those functions/commands/whatever they are called, I need to use? "noskipws"? "ws"?

why am I not supposed to use "gets()" anyway, what's wrong with it?

gets() is a worm, pretty literally. It does not respect the boundaries between the variable you intend to put it in, and other variables in memory, or other people's memory, etc.

Second, you need to learn the difference between a "tutorial" and a "reference". Although you do have a legitimate complaint, because I linked to the wrong page: getline - C++ Reference is where you're supposed to be. (I'd blame the pain meds, but it's only ibuprofen. Sorry.)

A common convention is to reserve fully capitalised names for macro names (though T is also a conventional template parameter name, but here Package would probably be better). It is good that you posted using code bbcode tags, but you should indent your code properly too.

Note that the return type for main is missing. This is illegal C++.

ok I got it now thanks, but for

Code:

template <class PACKAGE>
class KG_GC{
PACKAGE KG,GC;
public:
KG_GC(PACKAGE first,PACKAGE second){KG=first,GC=second;}
PACKAGE INSERT_KG_GC ();}; //class KG_GC
template <class PACKAGE>
PACKAGE KG_GC<PACKAGE>::INSERT_KG_GC (){
cin>>KG;
cin>>GC;
cout<<"KG:"<<KG<<"\n";
cout<<"GC:"<<GC<<"\n";};


main(){

double KG_TEMP,GC_TEMP;
KG_GC<double>KG_GC_TEMP(KG_TEMP,GC_TEMP);
cout<<KG_GC_TEMP.INSERT_KG_GC ();
}

it says "1.#QNAN" at the end, how do I get rid of it?

P.S. I used all caps because none of it is final, it's just sketchy stuff, and these are just parts of a bigger program which doesn't require return 0 (that's another story)

...Did you listen to what was suggested here?
The code is a mess. Fix it!

sorry, how is it a mess besides using for example <class PACKAGE> instead of <class T>?

how would I know how to fix something I don't know how to fix, for example "1.#QNAN" doesn't tell me anything and I try to search the internet but it doesn't tell me much

You fix it by listening to comments made by members. Here are two helpful ones:

Originally Posted by laserlight

A common convention is to reserve fully capitalised names for macro names (though T is also a conventional template parameter name, but here Package would probably be better). It is good that you posted using code bbcode tags, but you should indent your code properly too.

Originally Posted by Elysia

Note that the return type for main is missing. This is illegal C++.

Note the parts in bold.
Also, stop putting the ending braces on the same line. That is just obfuscating the code.

If you look up your "number" you should find things about NaN = Not a Number. Somewhere along the way you have done something awful in your calculations (or perhaps you are just interpreting some random check of memory as a double when it isn't; hard to say).

thanks but no thanks, I understand that it would be easier for everyone else to understand if I try to put every little thing in the same standard as everyone else, but sorry again, I prefer laying all those little things differently... the program does the exact same thing anyway

as for return, this is how I do it:

Code:

...
int main(){
...
do{
...
int B0;cin>>B0;switch(B0){
...
case  0:{return 0;}
...
 break;}//switch B0=18
 }//switch B0
 }while(1);//doodoo

 }//main

Originally Posted by llVIU

thanks but no thanks, I understand that it would be easier for everyone else to understand if I try to put every little thing in the same standard as everyone else, but sorry again, I prefer laying all those little things differently... the program does the exact same thing anyway

Unless you are working for a company or on a project that mandates a specific style, there is no standard style. However, there are commonly used styles and conventions. Pick one such style, and follow conventions when you do not have a good and compelling reason to do otherwise. If not, your code will be more difficult to read and understand, and possibly also more difficult to edit. This may not matter to you as a student, but it will matter should you do group projects and later work in a team after you graduate.

thanks but no thanks, I understand that it would be easier for everyone else to understand if I try to put every little thing in the same standard as everyone else, but sorry again, I prefer laying all those little things differently... the program does the exact same thing anyway

O_o

Came by to answer your "how do I get rid of it?" question, but then I read that post.

If you can't be bother to help yourself why should we be bothered to help you?

Soma

look, please stop with the irrelevant talk, does anyone know how I can fix the "1.#QNAN" error or not? I'd very much appreciate if I could be helped only with the "1.#QNAN" error and nothing else, *NOTHING* else please, thank you very much