[Qt-interest] anyone know why QDir::mkpath() isn't static?

[Alan Ezust]

On Tue, Apr 12, 2011 at 9:26 AM, Thiago Macieira <thiago at kde.org> wrote:
> 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
>
> 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?

Well, I really like the idea of QFileInfo... but it took a while to
understand its idiosynchracies.
I would like to mention a couple of things that annoy me that is
related to this:

I can't use QFileInfo::baseName() because it chops off things after
the first but before the last .
I would have reported it as a bug but it's documented that way so oh well.

I can't use QUrl::toLocalFile() because it truncates paths that
contain # and other weird characters.