Re: Global or not global

(singleton = global variable)?

It is global state that is a problem, not just global variables. And yes, singletons are also global state. So you win nothing by using a singleton over a global variable.

So you have several options: you can understand why global state is bad, and still decide to use it. Or you can go the OO route where the database handle is available.

Perl 6 - the future is here, just unevenly distributed

Comment on Re: Global or not global

Replies are listed 'Best First'.
Re^2: Global or not global by tobyink (Canon) on Jul 03, 2012 at 10:14 UTC
Indeed - global variables are a symptom of the underlying design problem, they're not a problem in themselves. `perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'`	[reply]
Re^2: Global or not global by BillKSmith (Monsignor) on Jul 30, 2012 at 02:41 UTC
In this case, I reluctantly vote for the global solution. The required object code would probably include most of the program so object variables would be little different than globals. The increase in code complexity would cancel any small improvement in encapsulation.	[reply]