[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Why DateTimes and Dates and Times?
From:       Stephen Kelly <steveire () gmail ! com>
Date:       2010-11-07 14:32:25
Message-ID: ib6d9p$du1$1 () dough ! gmane ! org
[Download RAW message or body]

John Layt wrote:

> On Saturday 06 November 2010 16:17:19 Stephen Kelly wrote:
>> Hi,
>> 
>> This is again something that is probably quite obvious, but I don't see
>> the reason for time objects and date objects like QDate and QTime when
>> QDateTime can represent in one object what the other two represent alone.
>> 
>> Is it something for locale specific issues, or is the answer obvious and
>> I haven't worked enough with those and similar classes to grok it?
>> 
>> All the best,
>> 
>> Steve.
> 
> Because that's how Qt wrote them ;-)  Mainly I suspect because of the
> memory used, and there are cases I guess where just a date or just a time
> in
> isolation is OK.  But in the global connected internet age I really wonder
> if we shouldn't be forcing devs to consider what a date really means in
> terms of different users timezone.
> 
> John.

I'm quite surprised that the reason might be just memory considerations. I 
had thought th difference wouldn't be huge.

python also has separate datetime, date and time classes btw.

All the best,

Steve.

[prev in list] [next in list] [prev in thread] [next in thread]