> This is puzzling, because, apart from the unix world where time_t is signed
> for sure (see http://en.wikipedia.org/wiki/Unix_time#Representing_the_number)
> I found indirect evidence that it should be signed on Windows, too:
> http://support.microsoft.com/kb/149471/en-us
> 

time_t FileName::lastModified() const
{
        [..]
        return d->fi.lastModified().toTime_t();
}

Windows might have signed time_t values, though QDateTime::toTime_t()
returns an uint. In case of error, 0xFFFFFFFF is returned.

http://doc.qt.nokia.com/latest/qdatetime.html#toTime_t

See my other mail too.

Vincent

Reply via email to