Re^3: DateTime parsing and midnight

Yes. That is a point in time. But the other string is a duration, as it is meant for the whole day, isn't it?

In any way, as you seem to want the two to be treated differently, you will have to do so.

Comment on Re^3: DateTime parsing and midnight

Replies are listed 'Best First'.
Re^4: DateTime parsing and midnight by pokki (Monk) on Nov 11, 2010 at 14:29 UTC
I finally got what you meant, sorry. I never thought of all-day events as having a duration, despite their name; on calendar applications they are usually marked once for the day, not as having a duration of 24 hours. The use case is more like "Foo's birthday" than "It will be Foo's birthday for 24 hours today", if you get my meaning. It all probably means I'll have to distinguish them by hand after all, before giving them to DateTime::Format::whatever. I was hoping there would be some way to recognize a DateTime object created with no time from a DateTime object created with 0:00 as the time. Well, if there ain't, there ain't. Thank you for your input!	[reply]
Re^5: DateTime parsing and midnight by Corion (Patriarch) on Nov 11, 2010 at 14:39 UTC
Ah - now I understand what these "whole day" entries are for. I think you will still need a marker for these entries, as they are special because they appear (at least on my phone calendar) without a duration bar. There is no way to distinguish a DateTime with a default time from a DateTime with a time portion of 0:00.	[reply]
Re^5: DateTime parsing and midnight by Anonymous Monk on Nov 11, 2010 at 18:49 UTC
Can you use duration = 0 seconds vs duration = undef? What about negative duration being a special case?	[reply]