Function Parameters in Powershell?

In V1, it really is just preference. Using the param statement has traditionally been more formal, but functionally its the same thing.

In V1, it really is just preference. Using the param statement has traditionally been more formal, but functionally its the same thing. You will probably see a lot more use of PARAM in PowerShell V2 because of the ability to add attributes to parameters, similar to attributes in C#.

Param ( Parameter( Mandatory=$true, Position=0, ValueFromPipeline = $true, ValueFromPipelineByPropertyName = $true) Alias("name") String $path ) Here you can specify the parameter attribute and a bunch of arguments to that attribute. You can also specify aliases and a number of other validation requiremets. Keith makes a couple great points as well.

You can use the param statement to pass parameters to annonymous scriptblocks (lambda expressions) or to a PS1 script.

Param() is required to specify the parameters for a script file and for scriptblocks: PS> $sb = {param($x,$y) $x + $y} PS> &$sb 1 3 4 Having it also be available for traditional functions is just a consistency thing IMO. It is nicer for advanced functions which tend to have a lot of baggage, er metadata, per parameter.

Always specifying parameters the same way improves readability.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.