Thread: Pointers & File I/O

If you dont understand me

Yep, that part.

It sounds like you want to pass a file pointer as an argument to a function correct?

You could do it one of two ways I suppose, if you are using classes, make the fstream var a class member. You could make it static as well, but I think the member approach is better.

If this is not in a class based program, you could make the file pointer global, or just pass the FILE pointer directly. You must pass the FILE as a pointer because when you call fopen you get back a pointer.

I am still a bit confused about what you want, but perhaps answers to my questions or comments will help us.

You can pass streams around by reference relatively freely, however this may not be quite what you want. If you want to search in a stream/file for a particular string you could do something like this

Code:

std::string search_line(const std::string &pat, std::istream &is) {
    std::string tok;
    while(is >> tok) {
        if(tok == pat) {
            std::string tail;
            std::getline(is,tail);
            return tok + tail;
        }
    }
    return "";
}
....
std::ifstream ifs("file.txt");
std::string line = search_line("joe",ifs);
if(!line.empty()) std::cout << "Found " << line << std::endl;

This will advance through a stream/file until a string exactly matches pat, then return that line from the token to the end of line.

You don't need to pass anything anywhere. In the makefile function, write out the file using an ofstream local to that function (so that it closes when the function ends). In the showname function, display the contents of the file using an ifstream local to that function (so that it closes when the function ends). As long as the file names are the same it will work. At worst all you need to pass is the filename as a string to each method if the name changes.

What if he wants to keep the file open? There may be instances where closing and reopening the file is a waste of time, especially if he has a loop going where he is writing/reading a file. Opening and closing it each cycle could be a tremendous waste of time, not to mention a bit lazy.

In this SPECIFIC case, it would be fine to do so, but its a perfectly valid thing to know how to pass input/output pointers to a function.