summaryrefslogtreecommitdiffstats
path: root/src/corelib
diff options
context:
space:
mode:
authorSimon Hausmann <simon.hausmann@nokia.com>2010-03-11 13:27:03 (GMT)
committerSimon Hausmann <simon.hausmann@nokia.com>2010-03-11 16:24:28 (GMT)
commit5058983c6ee286ca89598e0fed862f55250db26b (patch)
tree053513af2c6c4013e8d149adeda52d55fd3ec29d /src/corelib
parent41bd30db724aa5cb816f6dea2b9fc5fd2cf7351c (diff)
downloadQt-5058983c6ee286ca89598e0fed862f55250db26b.zip
Qt-5058983c6ee286ca89598e0fed862f55250db26b.tar.gz
Qt-5058983c6ee286ca89598e0fed862f55250db26b.tar.bz2
Doc: Removed lie that access to QBuffer is unbuffered.
In fact QIODevice still _does_ buffer access through QBuffer currently. Reviewed-by: Markus Goetz Reviewed-by: Joao
Diffstat (limited to 'src/corelib')
-rw-r--r--src/corelib/io/qiodevice.cpp3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/corelib/io/qiodevice.cpp b/src/corelib/io/qiodevice.cpp
index 662100a..c93f0c3 100644
--- a/src/corelib/io/qiodevice.cpp
+++ b/src/corelib/io/qiodevice.cpp
@@ -282,8 +282,7 @@ QIODevicePrivate::~QIODevicePrivate()
Certain flags, such as \c Unbuffered and \c Truncate, are
meaningless when used with some subclasses. Some of these
restrictions are implied by the type of device that is represented
- by a subclass; for example, access to a QBuffer is always
- unbuffered. In other cases, the restriction may be due to the
+ by a subclass. In other cases, the restriction may be due to the
implementation, or may be imposed by the underlying platform; for
example, QTcpSocket does not support \c Unbuffered mode, and
limitations in the native API prevent QFile from supporting \c