Also ((SystemNavigation default allImplementorsOf: #instance) select: #isMetaSide) size. "10" ((SystemNavigation default allImplementorsOf: #singleton) select: #isMetaSide) size. "1" This reminded me of this https://twitter.com/ID_AA_Carmack/status/575788622554628096 considering we already use a/an for parameters, this can be quite fitting. But some consensus would be nice⦠personally I don't really like that I have to think about the fact that it is a singleton, so The* + #new sounds interesting. Otherwise to me #current sounds much more fitting than #default (in fact I would expect them return different things if #current: has been used). Peter On Wed, Apr 8, 2015 at 11:37 AM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Sometimes I use #new
On 08 Apr 2015, at 11:31, Christophe Demarey < Christophe.Demarey@inria.fr> wrote:
Hi,
We use quite often the singleton pattern but when I need to use one, I always need to ask myself "What is the selector to get this singleton?". We use either aClass>>current, aClass>>default or aClass>>uniqueInstance. Could we agree on the selector to use and update existing code?
To get a quick overview, I searched about these methods in a Pharo4 image and get these results: ((SystemNavigation default allImplementorsOf: #default) select: #isMetaSide) size. "45" ((SystemNavigation default allImplementorsOf: #current) select: #isMetaSide) size. "40" ((SystemNavigation default allImplementorsOf: #uniqueInstance) select: #isMetaSide) size. "19"
Your opinion?
Christophe.