Revision as of 18:32, 12 May 2013 edit Diggory Hardy (talk \| contribs) 38 edits m →How do modules differ from singletons? ← Previous edit		Revision as of 18:45, 12 May 2013 edit undo Diggory Hardy (talk \| contribs) 38 edits two new sections Next edit →
Line 138: :Modules need not have single instantiations. The concept of modules does not require classes either. It's a much less well defined concept as far as I can tell. [[User:Diggory Hardy\|Diggory Hardy]] ([[User talk:Diggory Hardy\|talk]]) 18:31, 12 May 2013 (UTC) == History == This looks more like a short summary that should go at the top of the page. Mostly it's not history. [[User:Diggory Hardy\|Diggory Hardy]] ([[User talk:Diggory Hardy\|talk]]) 18:45, 12 May 2013 (UTC) == Advantages == This section is wooly (no citations, vague language) and is not balanced by talking about drawbacks (e.g. modifications of a module's interface having to touch on a lot of code, the advantages for testing only being realised with considerable extra work writing tests, and the often large amount of extra code required (over if logic)). Should it be deleted? Complemented by a "drawbacks" section? Renamed "comments"? [[User:Diggory Hardy\|Diggory Hardy]] ([[User talk:Diggory Hardy\|talk]]) 18:45, 12 May 2013 (UTC)

Talk:Modular programming: Difference between revisions