Issue 948 in moose-technology: mooseNameOn: uses signatureFromSmalltalkSelector

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

Issue 948 in moose-technology: mooseNameOn: uses signatureFromSmalltalkSelector

moose-technology
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 948 by [hidden email]: mooseNameOn: uses  
signatureFromSmalltalkSelector
http://code.google.com/p/moose-technology/issues/detail?id=948

FAMIXMethod mooseNameOn: aStream
has an interesting implementation.
Is there a special reason not to use
the signature when it is defined,
instead of the signatureFromSmalltalkSelector?

Doru wrote:
This is horrible! Indeed, we should use the signature there, and the  
signatureFromSmalltalkSelector should disappear (because it should be set  
at import time).

4.8 Development


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 948 in moose-technology: mooseNameOn: uses signatureFromSmalltalkSelector

moose-technology
Updates:
        Status: Fixed
        Labels: Milestone-4.8 Component-Famix

Comment #1 on issue 948 by [hidden email]: mooseNameOn: uses  
signatureFromSmalltalkSelector
http://code.google.com/p/moose-technology/issues/detail?id=948

(No comment was entered for this change.)

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev