On Jun 6, 2013, at 5:54 PM, Mariano Martinez Peck <[email protected]> wrote:
> Hi guys.
>
> I think I found a problem with class comments. The default method
> #classComment: in TClassAndTraitDescription does the following:
>
> classComment: aString
> "Store the comment, aString or Text or RemoteString, associated with
> the class we are orgainzing. Empty string gets stored only if had a
> non-empty one before."
> ^ self classComment: aString stamp: '<historical>'
>
> Why it puts a '<historical>' stamp instead of say "Author changeStamp" ?
>
> Nautilus uses this message. So as a consequence, when you edit and save a
> class comment with Nautilus, to get a <historical> stamp....
>
> I am using Pharo 2.0.
>
> Bug?
>
Yes!
Marcus
