Issue 4581 in pharo: trait method tagging is not consistent

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 4581 in pharo: trait method tagging is not consistent

pharo
Status: Accepted
Owner: [hidden email]

New issue 4581 by [hidden email]: trait method tagging is not  
consistent
http://code.google.com/p/pharo/issues/detail?id=4581

(SourceFiles sourcedDataAt:  (Point>>#dist:)  sourcePointer)
        'Point methodsFor: ''point functions'' stamp: ''lr 7/4/2009 10:42'''
       

SourceFiles sourcedDataAt: (ComposableMorph>>#newToolSpacer) sourcePointer
        'Trait method'


so protocol, stamp: .... got confused.

One of these days we will have to fix that


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4581 in pharo: trait method tagging is not consistent

pharo
Updates:
        Labels: Type-Bug

Comment #1 on issue 4581 by [hidden email]: trait method tagging is  
not consistent
http://code.google.com/p/pharo/issues/detail?id=4581

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 4581 in pharo: trait method tagging is not consistent

pharo
Updates:
        Status: Closed

Comment #2 on issue 4581 by [hidden email]: trait method tagging is  
not consistent
http://code.google.com/p/pharo/issues/detail?id=4581

With Pharo 2.0 now beta, time has come to review bug reports that have not  
seen any activity in 2012.
To keep the amount of issues managable, we close reports that have not  
drawn any attention for over one
year.

The reporter (and thus owner) of the issue should:

  -> check the issue in 2.0. Is it still relevant?
  -> If yes, just add a note to the report and we will be opened again.


As your issue has not seen any attention for over a year, please consider  
to give more information.
A good idea can be to send a mail to the mailinglist to get other people to  
help fixing the bug or
implementing an improvement.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker