http://blogs.msdn.com/b/powershell/archive/2007/01/09/2-2-equals-monday-evening.aspxI wanted to follow up on Jeffrey's post and one of the comments. It has to do with this example: PS&gt; [int]1/2 0.5 The reason that we get a double rather than an int is because of precedence. The conversion has a higher precedence than the divisionen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/powershell/archive/2007/01/09/2-2-equals-monday-evening.aspx#1440380Wed, 10 Jan 2007 00:22:47 GMT91d46819-8472-40ad-a661-2c78acb4018c:1440380John<p>I'm just guessing, but is it possibly when the types are incompatible that the first operand is used in this way?</p> <p>Internally, the + operator works as an overloaded function. &nbsp;When you use + with strings, it concatenates. &nbsp;When you use it with numeric types (floats, doubles and integers). &nbsp;Because .NET has a + operator that can add floats to integers, it uses that, and returns whatever that returns.</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1440380" width="1" height="1">http://blogs.msdn.com/b/powershell/archive/2007/01/09/2-2-equals-monday-evening.aspx#1440308Wed, 10 Jan 2007 00:01:24 GMT91d46819-8472-40ad-a661-2c78acb4018c:1440308nlhowell<p>I had no idea you were so musical.</p> <p>My guess is that PowerShell makes a special exception for division.</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1440308" width="1" height="1">http://blogs.msdn.com/b/powershell/archive/2007/01/09/2-2-equals-monday-evening.aspx#1440156Tue, 09 Jan 2007 23:04:52 GMT91d46819-8472-40ad-a661-2c78acb4018c:1440156Jeffrey L Whitledge<p>But you said in the previous post that the data type of the result is the data type of the first operand. So how does the int get converted to a double?</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1440156" width="1" height="1">