MFC, Are CFile::Read() and CFile::Write() Really Unbuffered?

Are CFile::Read() and CFile::Write() Really Unbuffered?

Author	Message
Andy Y #1 / 2	Are CFile::Read() and CFile::Write() Really Unbuffered? The docs claim that CFile::Read() and CFile::Write() are not buffered, yet when looking inside CFile::Open() source code, I notice that the ::CreateFile() used doesn't specify any special options for non-buferred I/O other than FILE_ATTRIBUTE_NORMAL (no way to specify any other attribute flags like FILE_FLAG_SEQUENTIAL_SCAN)... ------------------------------------------------------------------------ Andy Yee Corporate E-Mail: See Above Software Engineer Coporate Web Page: http://www.--.com/ Personal Web Page: http://www.--.com/ ~nde Question authority...and the authorities will question YOU! ------------------------------------------------------------------------
Sat, 22 Sep 2001 03:00:00 GMT

David Lownd #2 / 2	Are CFile::Read() and CFile::Write() Really Unbuffered? Quote: >The docs claim that CFile::Read() and CFile::Write() are not buffered, yet >when looking inside CFile::Open() source code, I notice that the ::CreateFile() >used doesn't specify any special options for non-buferred I/O other than >FILE_ATTRIBUTE_NORMAL (no way to specify any other attribute flags like >FILE_FLAG_SEQUENTIAL_SCAN)... Andy, I think that when the docs say they're unbuffered, it's referring to no additional 'c' run-time buffering such as the stream I/O has. Dave ---- My address is altered to discourage junk mail. Please post responses to the newsgroup thread, there's no need for follow-up email copies.
Sun, 23 Sep 2001 03:00:00 GMT

Page 1 of 1

[ 2 post ]