-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, funny...
Am 03.05.2007 um 04:26 schrieb [EMAIL PROTECTED]: >>> 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? Oups... No, its related to: "I'd suggest this refinement: an extra parameter that indicates whether the date is expected to be in the future or the past." Sorry. > >> 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. If I've convention, I don't need to guess. 8) > >> I think REALBasic has one, too. To know this convention should be >> enough. > > Enough for what? To know, what to do? 8)) > >> 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. Correct, solving the dilemma isn't possible in this case. But it should be well defined what to do, if you have to parse a 2- digit year; isn't it a convention? - -- Regards Vincent -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGOaJhKFUEqRtS0ZARAsMyAKCzFGAARjvbrjWb4TdVzbhYKgJYJwCgtpci B15VMbfybaqaj5D2XTFqzjk= =ezZj -----END PGP SIGNATURE----- _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
