Why does ‘$true -eq “string”’ returns $true? [duplicate]

Why does ‘$true -eq “string”’ returns $true? [duplicate]

This question already has an answer here:

Why is $false -eq “” true?

2 answers

In powerShell you compare a boolean with a string with the “-eq” operator it will always return the same boolean as I used to compare.
$shouldBeFalse = $true -eq “hello”
$shouldBeTrue = $false -eq “hello”

The variable $shouldBeFalse is $true.
The variable $shouldBeTrue is $false.
I had to use the “Equals” method:
$shouldBeFalse = $true.Equals(“hello”)

In this case $shouldBeFalse is $false.
But why returns the -eq operator with boolean these kind of results?


Solution 1:

PowerShell will always evaluate using the type of the left-side argument. Since you have a boolean on the left PowerShell will try and cast “Hello” as a boolean for the purpose of evaluating with -eq.

So in your case "hello" is converted to a boolean value [bool]"hello" which would evaluate to True since it is not a zero length string. You would see similar behavior if you did the opposite.

PS C:\> "hello" -eq $true

PS C:\> [bool]"hello" -eq $true

In the first case $true is converted to a string “true” which does not equal “hello” hence false. In the second case we cast “hello” to boolean so the -eq will compare boolean values. For reasons mentioned about this evaluates to True.

Another good explanation comes from this answer which might get your question flagged as a duplicate: Why is $false -eq “” true?

Solution 2:

$TRUE is > 0 and "hello" length > 0 so it is TRUE. $FALSE is == 0 and "hello" length < 0 so it is FALSE.

When you use Equals, the var are compared as strings, so $TRUE isn’t equal to hello -> FALSE.

source: http://blogs.msdn.com/b/powershell/archive/2006/12/24/boolean-values-and-operators.aspx

Related:  Variable Scopes Within PowerShell Nested Functions