On Wed, Dec 29, 2010 at 1:51 AM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
>
> 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.

Eliot we do not impose anything to the community. Please do not bash us we have enough to do without that!

Steph, /I'm/ not bashing. �I got bashed. �Suddenly the comments I'd put in VMMaker were to be banned by Pharo. �Look, the timestamp syntax if any, is defined by Utilities class>>changeStamp, along with the implicit restriction that the changeStamp can't contain an exclamation point, or it'll break parsing. �Utilities class>>changeStamp is essentially anything followed by date and time, because there are /no/ restrictions on what one sets the Author initials to be (some people use full name, some people use initials, some people use put other stuff in there, but it's free apart from the $!). �So to parse date and time one has to start at the end of the timestamp, go back two spaces and parse from there (ooh, difficult ;) ). �There's no need for anything else. �Why make life difficult for the community by imposing syntax when none existed before? �All you'll do is make work and frustrate people. �Is Pharo about helping or hindering? �I think it's about helping, but the above syntax restrictions don't feel like that. �KISS, right? �If you want to find the date or time in a timestamp start at the end, and leave the beginning free from interpretation.

2�

�
Apparently the code was like that and people (may be johan) started to make sense out of it.

Stef