10 Jan
2016
10 Jan
'16
11:56 p.m.
We did write more comments in the last version, but we would indeed benefit from more
details now that things should be more stable. If anyone is interested to contribute, it
would be of great help.
Doru
On Jan 11, 2016, at 12:48 AM, Dimitris Chloupis
<kilon.alios(a)gmail.com> wrote:
How much time it takes to write a short comment for a class ? One minute ? Two ?
Why not help people help you ? Is it not better to make it easier to cooperate ?
On Mon, 11 Jan 2016 at 00:31, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
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
--
www.tudorgirba.com
www.feenk.com
"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."
On Jan 10, 2016, at 5:24 PM, Sven Van
Caekenberghe <sven(a)stfx.eu> wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev 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.