[Pharo-project] Issue 3436 in pharo: #copyFrom: is broken (pharo at googlecode.com)
stephane.ducasse at inria.fr
Sun Jan 9 04:12:10 EST 2011
does anybody want to implement this hovering excellent idea.
On Jan 9, 2011, at 10:02 AM, Johan Brichau wrote:
> And yes, the rule of thumb is that one reads the comments (or implementation) of a method to understand it, rather than (only) trying to guess it's semantics from its selector.
> We all got used to coding like that in Smalltalk. However, it's _just_ a rule of thumb that comments on top of the method body should document the method. Not all methods do it, and people coming from different languages and development environments are not immediately comfortable because they 'need to look at the implementation of an API to understand it'. So, I think there is something we can learn from other development environments: in XCode, for example, you can request the documentation of a method in a small 'hover window' by a <ctrl>+<click> on the method name. I wonder if such a system in Smalltalk development environment would make documenting a method more important, and thus, force people to write and use it more....
More information about the Pharo-dev