global-state

So, I was reading the Google testing blog, and it says that global state is bad and makes it hard to write tests. I believe it--my code is difficult to test right now. So how do I avoid global state? The biggest things I use global state (as I understand it) for is managing key pieces of information between our development, acceptance, and production environments. For example, I have a static class named "Globals" with a static member called "DBConnectionString." When the application loads, it determines which connection string to load, and populates Globals.DBConnectionString. I load file

I'm dismayed. OK, so this was probably the most fun Perl bug I've ever found. Even today I'm learning new stuff about Perl. Essentially, the flip-flop operator .. which returns false until the left-hand-side returns true , and then true until the right-hand-side returns false keep global state (or that is what I assume.) Can I reset it (perhaps this would be a good addition to Perl 4-esque hardly ever used reset() )? Or, is there no way to use this operator safely? I also don't see this (the global context bit) documented anywhere in perldoc perlop is this a mistake? Code use feature ':5.10';

I just started working with Laravel. I need to rewrite a whole system I made some years ago, using Laravel 4 as base framework. In my old system I use to have a constant.php file with some constants declared, and a globals.php file which contained lots of array sets (For example, categories statuses, type of events, langs, etc.). By doing so, I could use something like foreach ( $langs as $code => $domain ) { // Some stuff } anywhere in my app. My question is, how can I store that info in the so called "laravel way". I tried using some sort of object to store this info, setting this as a