Simulating command line parameters

[LWC]

Is there a way to simualte command line parameters instead of having to:

• Compile the script.
• Enter Windows' DOS prompt and run the script with paramerers and/or create a shortcut.

every time you want to run the script (if it can't run without parameters)?

$cmdlineraw can be re-assigned but it doesn't affect $cmdline, which is a non editable constant. Is there any way around it?

Thanks!

[Melba23]

LWC,

If you are running your script in SciTE (at least in the full version you can get from here), you can use the <View - Parameters> menu selection to set up to 4 commandline parameters to test when you run.

M23

[Juvigy]

Yes - put a default parameters that will take effect if you start it without parameters.

[LWC]

Thanks, Melba23, it works!

But Juvigy, how to create default parameters is exactly the question of this topic (unless you just meant Melba23's solution).

[Tvern]

There's a bunch of ways you can make "default parameters", but here's a solution that can be easily applied to any script:

First use Ctrl+H to replace all instances of $CmdLine, with $aCmdLine, or any name you prefer.

Then add something like this to your script:

Global $aDefaultParams[3] = [2,"Param1","Param2"] ;set the default paramenters
If $CmdLine[0] Then ;if there are any parameters specified at all
    $aCmdLine = $CmdLine ;use the specified paramaneters
Else
    $aCmdLine = $aDefaultParams ;use the default parameters
EndIf
;$aCmdLine is used in the rest of the script.

I doubt this method has any advantages over the Shift+F8 option though.

Edited December 9, 2010 by Tvern

[MvGulik]

  On 12/9/2010 at 1:38 PM, 'Tvern said:

I doubt this method has any advantages over the Shift+F8 option though.

The advantages lies in "when". In that you general better of using that way when your in initial Dev-stated. After your code has reached a certain stage(lets say production) it becomes less useful, and it becomes better to remove or minimize that part.