aamesxdavid wrote:So I was about to post a new thread in regards to the mention of it in the Adventures videos, but I figured I'd revive an older thread instead.
Falco mentions that the text file they use logs every file the game is trying to access, etc. I was wondering how exactly that was done, and if a similar thing is possible in Python, which is what I'm currently working with. I can write to text files, but the only thing I know of dealing with an error is the "try" and "except" functions in Python. Assuming that every file load doesn't have a "try" (or the C++ equivalent) and individually write to the text file, how is this file written? I don't mind if you only have the C++ answer, as it's more of the programming theory that I'm looking for I suppose. Thanks!
I get what you're saying. We have a Debug class (I think it's a singleton) with a function that works like fprintf() does. Debug is initialized like so:
Code: Select all
void Debug::Initialize() {
debugFile,open("debug.txt", ios::out); //Clear the existing file or create a new one
debugFile.close(); //Don't leave it open (we might not actually do this, see end of post)
}
We also have a function that works like printf does in Debug, so then, for instance, our Level::Load is something like
Code: Select all
Debug& debug = Debug::GetInstance();
levelFile.open(filename...);
if (!levelFile) { //there was some sort of error while opening the file
debug.write("Error loading %s\n", filename);
return ERROR; //where error is just some constant or error code or something
}
...
if (!(something = new Something)) {
debug.write("Out of memory!\n");
return ERROR;
}
Our write() fn would open debugFile for append (ios::app) and then close it after writing to it. This is terribly slow. It would be faster to open the file once and then close it when the program terminates. Which we might actually do, I'm not totally sure anymore :)
We just write to it when something doesn't go our way, in other words, and the Debug class handles the file I/O. We don't do anything with exceptions, which is what try { } except { } says to me, but you would basically do the same thing but in your except block instead of with ifs.
Hopefully I answered your question. If you want to see how to do an ellipsis function (replace like %s with an argument, no definite number of arguments passed to the function), I can help you with that. Also, sorry for the ambiguity, I'm too lazy to open the source :D
too soon?).
