On May 02, 2007, at 23:22 UTC, Vincent Kroll wrote: > > 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. > > No, I don't think so!
You don't think so what? That someone's birthday should be assumed to be in the past? > There are some (different) conventions; for example: > http://support.microsoft.com/kb/246389/en > only one example... Yes, these are ways of guessing when you don't have any additional information about whether the date is in the future or past. My point is that in real situations, this extra information is often available, so it'd be good to make use of it. > I think REALBasic has one, too. To know this convention should be > enough. Enough for what? > For an unique date you have to use a date with a four-digit year > 'yyyy'. I think that would be a better way to solve this dilemma. No, that's a way to avoid the dilemma. But if you need to actually solve it (i.e., you really do need to parse dates that might have 2-digit years), then you should do it as well as you can. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Strout Custom Solutions _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
