No I like it as it is. Simple and straight to the point. And since browse could apply to a variety of things while browseClass is very specific, similarl to what Ben is saying. I would prefer it for example if I wanted to browse the metaclass of Object to have Object class browse while for the instance side a Object browse would do, That gives browse message a context sensitive/dependant meaning which for me is what OO is all about while your browseClass goes against the same principle. On other hand I have an allergy to camel case anyway :D On Tue, Nov 4, 2014 at 8:20 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
This one smells funny to me...
Object>>#browse ^ self systemNavigation browseClass: self class
A less surprising API might be: - Object>>#browseClass - and, Class>>#browse as implemented above
What do you think?
----- Cheers, Sean -- View this message in context: http://forum.world.st/Browse-anObject-tp4788401.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.