On 28 December 2010 19:04, Eliot Miranda <eliot.miranda@gmail.com> wrote:
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 http://code.google.com/p/pharo/issues/detail?id=3485
The documented format is:
Timestampstrings can be of the form: Â Â Â Â Â Â Â Â <authorname><date><time>. Â Â Â Â Â Â Â Â <authorname><date> Â Â Â Â Â Â Â Â <date><time> Â Â Â Â Â Â Â Â <date><time><authorname> Â Â Â Â Â Â Â Â <date><authorname> Â Â Â Â Â Â Â Â <historical>
wow thats incredible.. can you add there support for: <author-><time><-name><date> cause i prefer this format for myself? :)
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?
Information is useful, if it can be understood by system , which can extract three distinct fields, like <author> <comment> <date&time> but when information looks like a soup where different things put in random order and random <historical> format, then it is just garbage. Still, i agree it is useful, even in such messy form, but only to human reader, and unfortunately not to system, since it have no means to distinguish where this method comes from, who is author and what is datestamp of it. Would you like to query a system some day, like: 'show me all methods modified by Mr. Eliot Miranda in Dec 2010' ? If yes, then probably we should think about some formalism there. At least, please stop inventing new format types each other day, which will confuse already complex parser.
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.
obviously, pharo can't impose any rules to projects which developed outside pharo.
best Eliot
So may the best is to republish a method with the correct timestamp.
-- Best regards, Igor Stasenko AKA sig.