Proposal: consistency for dateFormat()

David Jarvie lists at astrojar.org.uk
Wed Jan 25 19:15:50 GMT 2006


On Sunday 22 January 2006 23:20, André Wöbbeking wrote:
> On Sunday 22 January 2006 22:29, David Jarvie wrote:
> > On Friday 20 January 2006 15:37, Jaros³aw Staniek wrote:
> > > Ah, OK, I can propose an enum for both booleans.
> > > But then we still couldn't have the default option in if we do not
> > > want to surprise developers, could we?
> > >
> > > KLocale::formatDateTime(const QDateTime &pDateTime, int options =
> > > DateTimeFormat::ShortDateTimeFormat),
> >
> > DateTimeFormat::Short would be better. There's no point in repeating
> > the "DateTimeFormat" bit.
>
> There is, have a look at Qt or
>
>   formatDateTime(foo, Short)
>
> versus
>
>   formatDateTime(foo, ShortDateTimeFormat)
>
> OK, ShortDateTimeFormat is really long, maybe we can meet in the
> middle :) What about ShortFormat?

But surely there will be a compile error unless it is qualified by the class 
name, i.e. DateTimeFormat::Short .

-- 
David Jarvie.
KAlarm author and maintainer.
http://www.astrojar.org.uk/linux/kalarm.html




More information about the kde-core-devel mailing list