Pretty obviously, file management code has to be completely bulletproof. Some things to consider are:
* Multiple tasks accessing the same file simultaniously - how do you handle several task trying to write to the same file at the same time? * Medium failure. All storage media is, to some extent, subject to failure. You have to ensure that you can detect and handle media failure. * Where do you store the file information? There are a number of approaches; you could use a FAT (file attribute table) , which is a simple system but, obviously, if you lose the FAT you lose the entire file system. More sophisticated systems use a database to hold file information - making searching for files much faster.
As far as C++ is concerned files do not have structures, they are simply raw data streams. It's entirely down to the programmer to determine what structures exist within the file and to interpret the data accordingly. C++ cannot do it for you.
data redundancy
Classes and structures can be put in a header file the same way you would use them in a main program; the only difference is that they are placed in a separate file, called a header file. Then, after creating a new file, include that new file with the definition by the use of the preprocessor #include statement.
Maintaining, servicing, and disposing of records Maintaining the file plan poperly retiring or transferring records
List two problems P2P file-sharing systems can cause.
List two problems P2P file-sharing systems can cause.
You will be responsible for maintaining the file plan You will be responsible for maintaining, servicing and disposing of records You will be responsible for the porperly retiring or transferring records
'struct tm' (time.h) and 'FILE' (stdio.h)
Determining what type of records your office is responsible for maintaining.
pee
File structures that remain after a file has been deleted
A log file is a text or data file that details what happens at a given time if a program is set to log activities and events that occur during its execution.