Marcus Denker wrote:
On Jun 10, 2013, at 6:56 PM, jtuc...@objektfabrik.de wrote:
Am 10.06.13 18:01, schrieb Marcus Denker:
Breaks the Principal of Least Surprise for those you want to attract from other dialects. They may end up with a strong opinion on it :)
I am not against reverting the inspect change.. but it should be documented well, else this will be changed again in the future.
Another thing is that starting from 3.0, I am sure that nobody will ever put "inspect" or "halt" anywhere as they will use meta-links
instead…
hmm. that is probably just 5 minutes away from Pharo's world domination ;-)
As long as Pharo is "Smalltalk inspired", people will probably come up with solutions they learned in Smalltalk. I have not yet come to be a frequent Pharo user, but coming from another Smalltalk dialect, I would probably face the same problem as Sabine mentioned it. I am not sure I use inspect in message cascades very often, because I tend to avoid cascades in methods that look or feel as if I may want to inspect preliminary results, so I am probably unlikely to tap into the same trap often. But if I would, I'd be scratching my head and ask myself what the heck this could ever be good for…
So maybe we can
-> add #inspector that returns the tool
-> make inspect be like it was before (with documentation).
Marcus
+1
|
