On Tue, Dec 28, 2010 at 8:47 AM,
<pharo@googlecode.com> wrote:
Comment #3 on issue 3485 by stephane.ducasse: VMMaker does not load on Pharo 1.2
The documented format is:
Timestampstrings can be of the form:
� � � � � � � �<authorname><date><time>.
� � � � � � � �<authorname><date>
� � � � � � � �<date><time>
� � � � � � � �<date><time><authorname>
� � � � � � � �<date><authorname>
� � � � � � � �<historical>
Says /who/? �When I created all these timestamps to document a refactoring change there was no documented restriction on timestamps I could see. �Why impose restrictions which have little value? �Why needlessly break compatibility? �That timestamp *contains useful information*. �Why ban it?
If you *want* VMMaker to load in Pharo you need to ensure that Pharo supports the timestamps *that exist* not the timestamps you want to impose on the community.
best
Eliot
So may the best is to republish a method with the correct timestamp.