{"id":11831,"date":"2016-04-22T09:56:37","date_gmt":"2016-04-22T16:56:37","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=11831"},"modified":"2016-04-23T14:47:39","modified_gmt":"2016-04-23T21:47:39","slug":"calling-a-method-without-parentheses","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2016\/04\/22\/calling-a-method-without-parentheses\/","title":{"rendered":"Calling a method without parentheses"},"content":{"rendered":"

Late breaking news from PowerShell Conference Europe 2016!!<\/strong><\/p>\n

During PowerShell MVP Chrissy LeMaire’s (@cl<\/a>) knockout session at PowerShell Conference Europe 2016, “My Journey to 200,000 Rows a Second” (don’t miss the recording; I’ll tweet as soon as it’s available), PowerShell Principal Developer Bruce Payette (@BrucePayette<\/a>) said that you can call the Where method without parentheses.<\/p>\n

\"Chrissy<\/a>

Chrissy LeMaire and Bruce Payette at PowerShell Conference Europe<\/p><\/div>\n

“It’s a syntactic twiddle,” he explained, as only Bruce can.<\/p>\n

In an exclusive interview, Bruce clarified that, beginning in PowerShell 4.0, you can call ANY method in PowerShell without parentheses if it meets the specified conditions.<\/p>\n

The Old Rules: Parentheses are required<\/h1>\n

Prior to PowerShell 4.0, parentheses were required for any method call, even if the method doesn’t have any arguments, because the PowerShell parser used the parenthesis to identify a method call and distinguish it from a request for a property value.<\/p>\n

(Get-Process Notepad).Name\u00a0\u00a0 \u2190 Property<\/span><\/code><\/p>\n

(Get-Process Notepad).Kill() \u2190 Method<\/strong> (see the trailing parentheses)<\/span><\/code><\/p>\n

The New Rules<\/h1>\n

Beginning in PowerShell 4.0, you can call ANY method in PowerShell without parentheses if the method meets the following conditions.<\/p>\n