On 25.10.2008, at 12:49, Oscar Nierstrasz wrote:
BTW, it would be cool to check this in the Pharo image.
What would be the Smalltalk expression to pop open a browser on all
methods that send messages that are not implemented? (Or simply to
return a list of those messages?)
Yes, there is
SystemNavigation>>#browseAllUnimplementedCalls
The only problem is that it does not highlight the message that is
detected. That can be a problem in large methods to find the
problematic one.
Marcus
- on
On Oct 25, 2008, at 12:35, Adrian Lienhard wrote:
Probably, "literals do:" instead of "literalsDo:" will work.
(Normally, methods to be removed should first be deprecated, which
apparently was not done in this case.)
Adrian
On Oct 25, 2008, at 12:22 , Oscar Nierstrasz wrote:
Hi,
I was trying out the refactoring engine, and tried to run the code
critic.
I got a message not understood in
SmalllintContext>>addLiteralsFor: which sends literalsDo: to its
argument aCompiledMethod.
This appears to be the only method in the Pharo-dev image that
sends this msg.
Any ida what the fix should be?
- on
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
