10 Jan
2016
10 Jan
'16
11:30 p.m.
I see the motivation, but things should go incrementally. If code should be highly
documented, with a high test coverage, friendly to API migration then well.. not much
happens…
Cheers,
Alexandre
On Jan 10, 2016, at 5:24 PM, Sven Van Caekenberghe
<sven(a)stfx.eu> wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I think that we should not integrate new classes
if they don't have a
class comment that follow the template.
+100
I can understand that when prototype, hacking, being generally productive inside Pharo,
you don't write comments at first. But once you go public, after some iterations, and
especially if you want to be integrated into Pharo itself, there is no excuse. We need
proper class comments, and comments for the main non-trivial public methods.