Stephen Compall <[email protected]> writes: > Anyone relying on DD/MM/YYYY as the default: > > Due to the unfriendliness of this to certain locales, and the > unfriendliness of MM/DD/YYYY to other locales, I changed it to ISO 8601 > YYYY-MM-DD format, which everyone should understand. The parser also > now parses in this format. > > See r1420:930aa57f38ef for details.
*sigh* I wrote that code and I needed DD/MM/YYYY. I have no problem with the date presentation format, as that can easily be changed, but I will now have to maintain a divergent version of the parser in my local branches, because the parser is totally hardwired to a single format. But, I guess that's what I get for contributing a half-baked regexp-based crappy parser in the first place... --J. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
