[Pharo-project] Issue 3591 in pharo: Implementors of #listMorph place it in different (or no) category
Status: New Owner: ---- New issue 3591 by sean.p.d...@gmail.com: Implementors of #listMorph place it in different (or no) category http://code.google.com/p/pharo/issues/detail?id=3591 Pharo1.2rc1 Latest update: #12320 What is (if any) the standard here? I usually follow Kent Beck's advice to put getters in 'private' unless they are meant to be public, and in that case, in 'accessing'. But here we have 'accessing'/'callbacks' (OB)/'user interface'. Sean
Updates: Status: FixProposed Labels: Milestone-1.3 Comment #1 on issue 3591 by marcus.d...@gmail.com: Implementors of #listMorph place it in different (or no) category http://code.google.com/p/pharo/issues/detail?id=3591 We have no official standard... but normally people follow Kent Beck for new code. 1.3 Core image seems good, just one "uncategorized" for #listMorph... fix attached. Attachments: RecategorizeListMorph.1.cs 1.5 KB
Updates: Status: Closed Comment #2 on issue 3591 by marcus.d...@gmail.com: Implementors of #listMorph place it in different (or no) category http://code.google.com/p/pharo/issues/detail?id=3591 in 13100
participants (1)
-
pharo@googlecode.com