If you're developing, you're...not...looking at the code? That's how I'm interpreting your comments. I don't see how it is possible to develop without looking at the code.
To reiterate, public documentation should be there for the user, internal documentation (i.e. private methods) and comments are there for the developers. Travis On Saturday, December 27, 2014 7:08:14 PM UTC-8, Nathann Cohen wrote: > > > That is few and far between, and putting it at the module or class > levels > > are quite intrusive. > > In a section named "technical details", you would find this intrusive ? > > > Having the background technical information > > (especially that about design patterns used or easily deciphered from > the > > code) adds useless clutter that benefits nobody. > > We need a way to convey that information to developers, and in this > specific case it happened that the developers did not see it. We need > to make it more visible than by letting it stay in the code. > > Nathann > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
