Named parameters with Scope

Heya,

I love named parameters (I even used them in batches), so I really want all
my scripts to support them. However I run into problem when I try to define
also scope:

Param (
[string]$Global:JobStorage = $(throw "You must specify folder where you
jobs are stored as parameter."), #Get folder where jobs are stored
[string]$GlobalebugLog = $("$pwd\S4M_EngineDebug.log") #Location of debug
log (log file from current session. Optional parameter
)

If scope ($Global is specified, -JobStorage "C:\Temp" won't work...

Not sure whether it is bug or feature - I can imagine it was implemented to
prevent situation like
Param (
[string]$Global:JobStorage = $(throw "You must specify folder where you
jobs are stored as parameter."), #Get folder where jobs are stored
[string]$Private:JobStorage = $(throw "You must specify folder where you
jobs are stored as parameter."), #Get folder where jobs are stored
)

Martin

Why are you scoping your variables? This is a dangerous practice unless you know exactly what you are changing and why. The best practice is that functions should never modify the global scope.