Thomas Dupriez wrote > I got stuck countless times when > reading pharo code, because there was a message send to a variable I > didn't know the type of, so I couldn't know which method was being > called (because there were multiple methods with that name in the > system). So the only solution was to place a breakpoint and get that > method to be executed.
That is an interesting perspective. I usually browse senders. This almost* always seems to work, except when the message selector is very generic and reused in different contexts (e.g. #next) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
