Re: [Pharo-project] Issue 3452 in pharo: GlorpDBX no longer loads due to garbled timestamp

Comment #5 on issue 3452 by ya...@rogers.com: GlorpDBX no longer loads due to garbled timestamp http://code.google.com/p/pharo/issues/detail?id=3452 The VisualWorks reference is in the timestamp of the Glorp source. It's likely from the original code developed in VW. Yes, a failed parse should return "DataAndTime new", I figured that out almost immediately afterwards. Here's new code, without a VisualWorks reference, but it does not catch all parse failures. The old code appeared to check for index out of range, but in fact let through a timestamp without any '/' characters. Attachments: SourceReference-parseTimestampFrom.st 1.3 KB