[MSH] $args bug

This doesn't seem right to me:

MSH:48 # function huh { write-host "args[0] is $args[0]" }
MSH:49 # huh 8.0
args[0] is 8[0]

and has in fact broken my "CD" replacement function.

 

MSH>function huh { write-host "args[0] is $($args[0])" }
MSH>huh 8.0
args[0] is 8

hmm, also not what I expected

gr /\/\o\/\/

 

MSH>function huh { write-host "args[0] is $args" }
MSH>huh 8.0
args[0] is 8

no, same as before

 

MSH>function huh { write-host "args[0] is $args" }

function huh { write-host "type of args is $($args.GetType().Name)`ntype
of args[0] is $($args[0].GetType().Name)" }

MSH>huh 8.0
type of args is Object[]
type of args[0] is Double

Beta 3 evaluates numeric arguments

Neville.

 

function huh {param([string]$first) write-host "type of first is
$($first.GetType().Name)`nvalue of first is $first" }

MSH>huh 8.0
type of first is String
value of first is 8.0

Neville.

 

Yeah that is what is happening. 8.0 is converted to a numeric (double) and
then when you try to use it as a string you get the default formatter
behavior for doubles (I guess) which doesn't display trailing zeros.

Just out of curiousity, what problem did this change in behavior fix? This
is going to make it a bit of a pain to specify directories with names like
8.0 (->8), 9.0 (->9), 10.5020 (->10.502), 11.500 (->11.5), etc. For
example:

Directory: Microsoft.Management.Automation.Core\FileSystem::C:\Temp


Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 1/12/2006 10:42 PM 8

Doh! That created a directory called 8 instead of 8.0. Better hope the user
notices that MSH didn't do quite what they intended. :-(

 

mkdir 8.0

I don't know about mkdir (I zap all the legacy aliases) but new-item -type
directory 8.0 works.
This is because the expected parameter type is string.
Functions and scripts can get the same behaviour using param([type]name)

Neville.

 

This problem is in both the "md" and "mkdir" functions because they use
$args instead of strongly typed parameters.

 

I've filed a bug on this for you.

--
Lee Holmes [MSFT]
Microsoft Command Shell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

-----Original Message-----
From: Keith Hill [MVP]
Posted At: Friday, January 13, 2006 10:31 AM
Posted To: microsoft.public.windows.server.scripting
Conversation: [MSH] $args bug
Subject: Re: [MSH] $args bug

This problem is in both the "md" and "mkdir" functions because they use
$args instead of strongly typed parameters.