[Canberra-pm] do read-local.config

[Jepri]

The do.config file can still call functions, which is the right way to 
be doing it.  Altering variables in other modules is somewhat naughty.



Michael James wrote:
> In the perl cookbook it suggests a good way to keep
>  local configuration details out of a larger and messier script
>  is to put normal perl code into a separate file and  "do"  it.
>
> But in a throwaway line (middle of page 328) it says,
>  of course neither the doer nor the done will have access
>  to the other's lexical (my) variables.
>  
> Hang ON! Lets get this clear,  the  done.config  file
>  can't create a variable visible to the calling program,
>  nor see a pre-existing variable to change it.
>
> What's the point?
>
> Can any of you lexicographers explain
>  a way around this, to a bear of limited scope?
>
>