René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Why do handled exceptions show in ErrorVariable?","articleBody":"When you use try/catch and handle an exception, it still shows up in the global `$Error`, and _more importantly_, in the ErrorVariable.\r\n\r\nIs there any way to actually prevent handled exceptions from leaking into the ErrorVariable? Is there any way for a caller to determine that they are **not,** in fact, errors, but expected results that were dealt with by the function?  That is, how does a caller distinguish the errors that matter?\r\n\r\nConsider a simple example:\r\n\r\n```posh\r\nfunction Count-Parameters {\r\n    [CmdletBinding()]\r\n    param([Parameter(ValueFromRemainingArguments)]$Parameters)\r\n    try {\r\n        $Parameters.FasterMethod()\r\n    } catch {\r\n        $Parameters.Count\r\n    }\r\n}\r\n\r\n$Count = Count-Parameters # Everything is fine\r\n\r\n$Count = Count-Parameters This One Has Four # Still fine\r\n\r\n# But then my paranoid \"best practice\" fanatic does something like this:\r\n$Count = Count-Parameters -ErrorVariable noCount\r\nif(!$Count -and $NoCount) { \r\n   Write-Warning $noCount\r\n}\r\n```\r\n\r\nHow can I stop the error variable from containing these things that I explicitly handled?","author":{"url":"https://github.com/Jaykul","@type":"Person","name":"Jaykul"},"datePublished":"2017-05-12T02:43:20.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":20},"url":"https://github.com/3768/PowerShell/issues/3768"}