Thread: Chat BOT

classes dont havta be in seperate files

Well, if you place them into separate .cpp files, you'll have to compile them separately, then link the .obj files when building the program. A good newbie way is to place the functions in separate header files, and just #include them with your program. Cheap and easy

In the header, just do:

char * GetBytes( const char filename[], int * num_bytes) {
//...code
}


Then in the main.cpp file:

int main() {
char * bytes;
int amount;

bytes = GetBytes("response.txt", &amount);

bytes[amount-1] = '\0';

//...code...

}

Okee... Well, from what I know, these are the main purposes of headers:

-For classes:
-put the class declaration (or whatever you call it) in (classname).h
-put the implementation (or whatever you call it) in (classname).cpp

i.e.

Code:

//this is classname.h

class Classname
{
   public:
      void changeData(int n);
      int getData();
   protected:
      int data;
};

//this is classname.cpp

#include "classname.h"

void Classname::changeData(int n)
{
   data = n;
}

int Classname::getData()
{
   return data;
}

Then in main.cpp (or whatever you call it)

Code:

#include "classname.h"

int main()
{
   Classname myObject;
   myObject.changeData(5);
   cout << "myObject.data = " << myObject.getData();
   return 0;
}

Another purpose is to stick related functions/macros together:

Code:

//this is anglestuff.h

#define PI 3.1415926535897932384626
#define DEGREES_TO_RADIANS(degrees) ((degrees) * (PI / 180))
#define RADIANS_TO_DEGREES(radians) ((radians) * (180 / PI))

float getRefAngle(float angle)
{
   if(angle >= 0 && angle < 90)
      return angle;
   else if(angle < 180)
      return (180 - angle);
   else if(angle < 270)
      return (angle - 180);
   else
      return (360 - angle);
}

The last (I think) reason for using separate headers is, of course, just to confuse people and make the code impossible to understand. As for how the multiple-cpp's work, look at the classes example ;) They're for if you have the function prototype in a header and the definition in a cpp file.

**EDIT**

#include "openfile.h"
#include "closefile.h"
#include "readfile.h"

No, that is probably not a good idea :) Instead, you'd probably want to do this:

Code:

#include "myfilestuff.h"

Or, on the other hand, you could just do file i/o like normal people do it, and do the opening and stuff manually :P

No prob(?) lol.

I have been thinking about how one could implement my previous idea. Here is what i have come with (scrawled on the back of a geography worksheet).

When the user asks a question, do the following:
change the case
filter out uneeded words and characters (articles, punctuation, etc.)
try to find a match.
If you find a match, feed back the related answer.
if you don't:
-counter it (as before described)
-write it into the file
-write the user's response to the file
reply.

To distinguish the questions from other statements and related words, questions could either have a separate file (questions.txt) or have a separate range of id's. The related answer(s) would have the same ID and probably be in a different file (answers.txt) or another section of the main file.

The bot should also randomly ask the user a question and record the feedback so the bot can fuel it's own answer-repository.

When the bot is parsing the input, the bot could have a list of names (which are added to every time the user logs in) that it replaces with %s for subject if it finds them.

Also, to make the conversation more interesting, the bot could have a long list of generic starements and replies that have a %o in then (for object) that it uses to keep the conversation going. This (along with a variable containing the object and some way to filter out the object of conversation) would make the bot seem more coherent and intelligent.

That's all for now,
~Inquirer

You haven't gotten past opening the file yet?? Psst... try #include <fstream> And then look into std::ifstream and std:fstream.

P.S.
I hope I'm not slighting your intelligence; if you already knew the stuff very well, feel free to ignore me

i'm mostly just putting the ideas out there for when i get around to making my own. I like getting my ideas out there to be chewed up, mixed around, and spat back out (pardon the metaphor) just to see if they get improved anyo or if it is possible or a waste of time, etc.

P.S. an O.K. tutorial on file opening and stiff i found at http://www.cpp-home.com/FileIO_tutorial.php . The one i learned from isn't online anymore, and i don't know where it went.

//edit

P.P.S. In the tutorial i gave you, beware of the bad programming practices he uses (void main() etc.) and the fact that he calls quotes inverted commas. good luck!

edit//

~Inquirer

Wasn't there supposed to be an online "Sam's teach yourself c++ in 21 days"? That's a good place to look.