summaryrefslogtreecommitdiffstats
path: root/src/corelib/io/qabstractfileengine.cpp
diff options
context:
space:
mode:
authorRobert Loehning <robert.loehning@nokia.com>2010-07-20 16:19:52 +0200
committerRobert Loehning <robert.loehning@nokia.com>2010-07-20 16:22:07 +0200
commit9d95c2f032df55c2a1865f049dd8dc76ea924c83 (patch)
treef284be3e9cac2971ac9c17437fde030928de6232 /src/corelib/io/qabstractfileengine.cpp
parentbf7ffca088904c6872715a588a9c4e3dd0904fc8 (diff)
doc: Fixed typos in QAbstractFileEngineIterator
Reviewed-by: Alessandro Portale
Diffstat (limited to 'src/corelib/io/qabstractfileengine.cpp')
-rw-r--r--src/corelib/io/qabstractfileengine.cpp6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/corelib/io/qabstractfileengine.cpp b/src/corelib/io/qabstractfileengine.cpp
index e239ee99f3..d6b6f1136b 100644
--- a/src/corelib/io/qabstractfileengine.cpp
+++ b/src/corelib/io/qabstractfileengine.cpp
@@ -818,7 +818,7 @@ bool QAbstractFileEngine::unmap(uchar *address)
You can call dirName() to get the directory name, nameFilters() to get a
stringlist of name filters, and filters() to get the entry filters.
- The pure virual function hasNext() returns true if the current directory
+ The pure virtual function hasNext() returns true if the current directory
has at least one more entry (i.e., the directory name is valid and
accessible, and we have not reached the end of the entry list), and false
otherwise. Reimplement next() to seek to the next entry.
@@ -828,7 +828,7 @@ bool QAbstractFileEngine::unmap(uchar *address)
function is provided for convenience; it returns the full path of the
current entry.
- Here is an example of how to implement an interator that returns each of
+ Here is an example of how to implement an iterator that returns each of
three fixed entries in sequence.
\snippet doc/src/snippets/code/src_corelib_io_qabstractfileengine.cpp 3
@@ -959,7 +959,7 @@ QString QAbstractFileEngineIterator::currentFilePath() const
/*!
The virtual function returns a QFileInfo for the current directory
entry. This function is provided for convenience. It can also be slightly
- faster that creating a QFileInfo object yourself, as the object returned
+ faster than creating a QFileInfo object yourself, as the object returned
by this function might contain cached information that QFileInfo otherwise
would have to access through the file engine.