Need an advice
Hi!
I need an advice about the error checking for files. I'm writing a BIG project and I'm checking some values inside the setup file.
Now I'm asking you guys what would be better.
If I check the file, if it is not NULL when opened, at the start of the program or I check the file everytime it is opened and checked for the values?
Current projects:
1) User Interface Development Kit (C++)
2) HTML SDK (C++)
3) Classes (C++)
4) INI Editor (Delphi)
assuming it's a setup file, it's probably relatively small. you could load it into memory and avoid the whole problem. just check once.
Well if you were going to write to the file (I'm assuming you will at some stage), you should always check to see if the file is NULL. If the file was NULL, obviously it wouldn't contain any data. If it isn't NULL, then you would just need to read in the values.
alpha561
"You don't want to sell me death sticks"
(Can't seem to edit the above posts for some reason)...
What I meant was that when dealing with files (reading or writing to them) you should always check to see if the file is NULL. Again, as I said before, if the file was NULL, obviously it wouldn't contain any data. If it isn't NULL, then you would just need to read in the values. I would say, only check once, at the very start.
Last edited by alpha561; 05-23-2002 at 11:34 PM.
alpha561
"You don't want to sell me death sticks"
To check if the file is NULL is only one line if code. So why not be safe. That way you would never have to worry about it. I would even go as far as to say you can never have too much error checking. People are idiots, and god knows what someone can do to your program. That is my opinion.
'During my service in the United States Congress, I took the initiative in creating the Internet.' - Al Gore, March 9, 1999: On CNN's Late Edition
ALWAYS CHECK RETURN VALUES !!!
Ok, I will always check the return values.
Current projects:
1) User Interface Development Kit (C++)
2) HTML SDK (C++)
3) Classes (C++)
4) INI Editor (Delphi)
