>> >> >> I had made the fixes myself, creating a new class for dates (I don't need >> the complexity of Date just for determining if a date is past, I don't need >> date arithmetic either). I just wanted to inform, mainly because the bug >> seems to be still present in Pharo 3.0. >> >> Anyway, your solution does not work for the 'd/m/y' pattern, although it >> does for 'd/m/yy'. > > Depends on what a single y means, right ? > >> I could write the tests you suggest, if you think they are interesting. > > Yes, please do: with a good set of tests, we can discuss using concrete > examples.
Please :) We love tests!
