When doing comparison operations, PowerShell will automatically attempt to coerce the object on the right-hand side of the operator to match the type on the left-hand side.
In the case of coercing [string]
to [bool]
, any non-null string will evaluate as $true
, and a null string will evaluate as $false
. See blog post Boolean Values and Operators for more information about automatic conversion of different data types to boolean values.
This sometimes leads to unexpected results:
PS C:> [bool]"$false"
True
The string value of $false
is 'False', which is a non-null string and evaluated to $true
when cast back to [bool]
.
It also makes comparison operations non-commutative when the operands are of different data types:
PS C:> '' -eq $false
False
PS C:> $false -eq ''
True
In the first comparison the value $false
is auto-cast to a string in order to match the type of the first operand (''
), so you're actually comparing '' -eq 'False'
, which evaluates to $false
.
In the second comparison the string ''
is auto-cast to a boolean, again in order to match the type of the first operand ($false
), so this time you're actually comparing $false -eq $false
, which evaluates to $true
.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…