in reply to Re: Re: Access Log Reader
in thread Access Log Reader

This puzzled me: I originally put the config vars, as you suggest, at the top of the script. But then I thought I shouldn't do that, because the received wisdom seems to be that one shouldn't allow proliferation of what are effectively global variables.

The general wisdom is that one shouldn't proliferate global state. Configuration items aren't stateful. They are essentially read-only, named constants. Non-constant global variables, particularly when they're set frequently from all over a program, can make that program wickedly hard to understand. Not so with constants.

If you want to be doubly righteous, you can use constant to prevent someone from accidentally writing to your configuration items.

In Section Code Catacombs