HasNext() returns true when the Qstring passed to QDirIterator is null

Reply to HasNext() returns true when the Qstring passed to QDirIterator is null on Wed, 04 Jun 2014 15:11:14 GMT

[[global:former-user]] — Wed, 04 Jun 2014 15:11:14 GMT

Here is the entire code including my fix:
@void Demo::FindAllSubDirs(PathList &list)
{
// A container to store the subdirectory paths
PathList tempList;

for (PathList::iterator itr = list.begin(); itr != list.end(); ++itr)
{
tempList.push_back(*itr);
if(!(QString((*itr).c_str()).isEmpty()))
{
QDirIterator Obj(QString((*itr).c_str()), QDir::AllDirs | QDir::NoDotAndDotDot | QDir::Hidden, QDirIterator::Subdirectories);
while (Obj.hasNext())
{
Obj.next();

if(Obj.fileInfo().isDir()) 
{
 std::string tempDir = Obj.filePath().toStdString() + "/";
 tempList.push_back(tempDir);
}

}
}
}

list.clear();
list = tempList;
}
@
I also replace the QDirIterator line with this line as suggested and YES it does fail as Obj.hasNext() returns true and should return false:
@QDirIterator Obj(QString(""), QDir::AllDirs | QDir::NoDotAndDotDot | QDir::Hidden, QDirIterator::Subdirectories);@

The list requires a null as the first entry in the list.

Reply to HasNext() returns true when the Qstring passed to QDirIterator is null on Tue, 03 Jun 2014 20:11:06 GMT

MuldeR — Tue, 03 Jun 2014 20:11:06 GMT

What is the "expected behavior" for iterating an empty string anyway? It's obviously not a valid directory, so what would you expert? The result probably is undefined. Or does it implicitly iterate the current directory ???

(In the later case, the result depends on whatever happens to be your "current" directory - which is never a good idea)

Reply to HasNext() returns true when the Qstring passed to QDirIterator is null on Tue, 03 Jun 2014 19:54:21 GMT

SGaist — Tue, 03 Jun 2014 19:54:21 GMT

Hi and welcome to devnet,

Where does "QString((*itr).c_str())" come from ?

I just tested with 4.8.6 replacing QString((*itr).c_str()) with QString("") and it does work as expected.

Reply to HasNext() returns true when the Qstring passed to QDirIterator is null on Tue, 03 Jun 2014 17:43:58 GMT

[[global:former-user]] — Tue, 03 Jun 2014 17:43:58 GMT

Hi All

In the end I coded a work around. I now check the Qstring and if it is empty then I do not call QDirIterator. What I really need to know is did I find a bug in 4.8.6 or a new feature?