
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
698
|
Chapter 12: Filesystem I/O
it would be displayed by the ReadAllBufferedLog method as follows:
This is th10
e first li10
ne.
100
10
This is th10
e third li10
ne.
5
Notice that at the end of every 10th character (the buffer is a char array of size 10),
the number of characters read in is displayed. During the last read performed, only
five characters were left to read from the file. In this case, a
5 is displayed at the end
of the text, indicating that the buffer was not completely filled.
Discussion
There are many mechanisms for recording state information about applications,
other than creating a file full of the information. One example of this type of mecha-
nism is the Windows Event Log, where informational, security, and error states can
be logged during an application’s progress. One of the primary reasons for creating a
log is to assist in troubleshooting or to debug your code in the field. If you are ship-
ping code without some sort of debugging mechanism for your support staff (or pos-
sibly for you in a small company), we suggest you consider adding some logging
support. Any developer who has spent a late night debugging a problem on a QA
machine or, worse yet, at a customer site, can tell you the value of a log of the pro-
gram’s actions.
If you are writing character information ...