Globals or objects?

[tinnews at isbd.co.uk]

Aahz <aahz at pythoncraft.com> wrote:
> In article <47bd7ffe$0$514$bed64819 at news.gradwell.net>,
>  <tinnews at isbd.co.uk> wrote:
> >Aahz <aahz at pythoncraft.com> wrote:
> >> In article <72b59db8-ec9c-480a-9ae7-92a69acb70a6 at 41g2000hsc.googlegroups.com>,
> >>  <MartinRinehart at gmail.com> wrote:
> >>>
> >>>I had a global variable holding a count. One source Google found
> >>>suggested that I wouldn't need the global if I used an object. So I
> >>>created a Singleton class that now holds the former global as an
> >>>instance attribute. Bye, bye, global.
> >>>
> >>>But later I thought about it. I cannot see a single advantage to the
> >>>object approach. Am I missing something? Or was the original global a
> >>>better, cleaner solution to the "I need a value I can read/write from
> >>>several places" problem?
> >> 
> >> The advantage of the global singleton is that it is a container; 
> >> therefore, its contents are mutable and you don't need to keep using the 
> >> ``global`` statement.
> >
> >.... but you do keep having to use a longer reference to the value so
> >what have you won?
> 
> Clarity, simplicity, robustness

Clarity - why is it clearer?

Simplicity - no, you've added an extra layer.

Robustness - how?

-- 
Chris Green