[Qt-interest] anyone know why QDir::mkpath() isn't static?
Thiago Macieira
thiago at kde.org
Tue Apr 12 18:26:31 CEST 2011
Em terça-feira, 12 de abril de 2011, às 09:19:38, Scott Aron Bloom escreveu:
> I have found there are a number of little idiosyncrasies in the QFile,
> QFileInfo, and QDir code that can be confusing and worst case create a
> bug.. You just get used to them
>
> With mkpath... I would prefer if there was a static as well as a non-static
> member... I wouldn't even mind if the QDir threw an assert on the static
> member if the path sent in was relative.
For those interested, we're still having a discussion on the ugliness and
wrongs of QFile, QDir and QFileInfo in the #qt-labs channel. There's a lot
that could be done better and the developers agree.
The question is: when the time comes for when a source-incompatible is
permitted, what is better, to keep compatibility with thousands of existing
programs or to make a new, better but incompatible API?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20110412/97b20af6/attachment.bin
More information about the Qt-interest-old
mailing list