Parsing text files.

I'm trying to use an if statement with a bunch of different phrases that are accessible outside of the code, and I determined the best way to do this at my skill level would be to parse a text file.

E.G. I would make a list of names and then any time someone input one of those names into the field I would create, they would get one message, and if the name wasn't in the file, they would get another.
If someone could help me figure out how to do this it would be much appreciated.

Doing my best to understand what you mean . . .

In other words, you are creating a list of names, let's say, "names.txt", that contains something much like:

Code:

Allen
Brian
Crystal
David
Ellen

If someone enters the name "Brian", then your program will print "The name 'Brian' is in the list of names." -- whereas, if they enter "Varun", then the program will print "The name 'Varun' is not in the list of names."?

If so, then you will need to use ifstream. One example of a program that reads in words, then prints them out to the screen on their own lines could be:

Code:

#include <iostream>
#include <fstream>
#include <string>
#include <cstdlib>

int main(int argc, char *argv[]) {
    if(argc != 2) {
        std::cout << "usage: " << argv[0] << " filename" << std::endl;
        exit(1); /* NOTE: I'm not sure, in C++, if exit() is actually std::exit() or not. Probably. */
    }
    std::ifstream file(argv[1]);
    if(!file.is_open()) exit(1);
    bool done = false;
    do {
        std::string word;
        file >> word;
        std::cout << word << std::endl;
        if(file.eof()) done = true;
    } while(!done);
    file.close();
    return 0;
}

In C++, it is possible to compare strings against each other (string1 == string2), since operator==(const std::string &) is implemented by default.

That should be enough to get you started, at least.

Originally Posted by strange

Doing my best to understand what you mean . . .

In other words, you are creating a list of names, let's say, "names.txt", that contains something much like:

Code:

Allen
Brian
Crystal
David
Ellen

If someone enters the name "Brian", then your program will print "The name 'Brian' is in the list of names." -- whereas, if they enter "Varun", then the program will print "The name 'Varun' is not in the list of names."?

If so, then you will need to use ifstream. One example of a program that reads in words, then prints them out to the screen on their own lines could be:

Code:

#include <iostream>
#include <fstream>
#include <string>
#include <cstdlib>

int main(int argc, char *argv[]) {
    if(argc != 2) {
        std::cout << "usage: " << argv[0] << " filename" << std::endl;
        exit(1); /* NOTE: I'm not sure, in C++, if exit() is actually std::exit() or not. Probably. */
    }
    std::ifstream file(argv[1]);
    if(!file.is_open()) exit(1);
    bool done = false;
    do {
        std::string word;
        file >> word;
        std::cout << word << std::endl;
        if(file.eof()) done = true;
    } while(!done);
    file.close();
    return 0;
}

In C++, it is possible to compare strings against each other (string1 == string2), since operator==(const std::string &) is implemented by default.

That should be enough to get you started, at least.

Why are you using exit(1)? If I'm not incorrect, it simply terminates right then and there, and doesn't clean up the stack or anything. This means your file object is leaking memory in case of failure.

If it doesn't affect stack objects in the nearest scope, then it definitely affects everything else.
On top of that, it's pointless. You can just throw a return in there, and the stack frame gets cleaned up properly.

I know it might be a big issue in this particular program, but seeing as you used it two times in this very small program, where you should/could have used return, it looks like you have a bad habit that you shouldn't be teaching others. No offense.

Originally Posted by IceDane

Why are you using exit(1)? If I'm not incorrect, it simply terminates right then and there, and doesn't clean up the stack or anything. This means your file object is leaking memory in case of failure.

If it doesn't affect stack objects in the nearest scope, then it definitely affects everything else.
On top of that, it's pointless. You can just throw a return in there, and the stack frame gets cleaned up properly.

I know it might be a big issue in this particular program, but seeing as you used it two times in this very small program, where you should/could have used return, it looks like you have a bad habit that you shouldn't be teaching others. No offense.

exit - C++ Reference

Originally Posted by valaris

exit - C++ Reference

Oops. My bad. I guess I should have checked that out before going with something someone had told me.

Thanks a lot, strange. That's exactly what I was looking for. You were a big help.
Is there a name for this?

Originally Posted by IceDane

Why are you using exit(1)?

. . .

I know it might be a big issue in this particular program, but seeing as you used it two times in this very small program, where you should/could have used return, it looks like you have a bad habit that you shouldn't be teaching others. No offense.

You are correct, it is a very bad habit that I have. And you're right, I shouldn't be teaching others my bad habits.

I realized after I posted it that I could have just used return, but I was tired at the time and didn't feel like editing it. (Excuses, excuses . . .)

mwesclark: I would personally call it an argument, but I don't think that's what you were referencing . . .