On 2-May-07, at 3:37 PM, [EMAIL PROTECTED] wrote:
> On May 02, 2007, at 20:58 UTC, Vincent Kroll wrote:
>
>> This one: <http://rb.sgarman.net/validDate.php>
>
> That's neat. But if you're going to write your own date parser that
> may need to handle 2-digit years, I'd suggest this refinement: an
> extra
> parameter that indicates whether the date is expected to be in the
> future or the past. If asking the user for their birthday, for
> example, you'd specify past; if asking for the date of their next gala
> bash, assume future. Then, when somebody puts in 10/29/71, you won't
> need any extra steps to avoid making the silly assumption that they'll
> be born in 2071.
>
> My $0.02,
> - Joe
I think the intent was to do what ever had been assumed in ParseDate
that no longer works like people expected
So far it seems to work really well but it is still dependent on
local date settings.
I've tried lots here like mm/yy/dd, yy/dd/mm, mm/dd/yy and mm/dd/yyyy
with all kinds of separators like (;{' and even letters
I know of no GuessDate that can grok ambiguous things like 01/02/03
and figure out what was intended (which seems to be what folks
expected ParseDate to do)
I'm thinking THAT would have to be part of the ESP plugin :)
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
