On Thu, Dec 19, 2013 at 05:32:57PM +0000, Stephen Patterson wrote: > [...] I'm considering changing this to ISO-SQL standard - > yyyy-mm-dd. What's the best way of communicating this change & > managing things during changeover?
As you're well under the magic 1.00 version number, you could probably just change it and mention this in the release notes. Giving useful error messages will ease the transition. I tend to imagine that anyone pointint a 0.03 module at a real bank account will be reading every line and subsequent diff! Where the date is received by a method (I saw a parameter to new), you could translate it... adding baggage, to be removed later or handed off to Date::Parse. Where the date is returned (I saw a list of transaction hashrefs) maybe you can include both under different names. For a hashref this is untidy, but if it were instead an object you could supply two methods which give the different formats. Then deprecate one, give warnings when it is called, and remove it in later releases. Is that the kind of answer you were looking for? -- Matthew -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
