PowerShell5-Tokenize+Expression-Function+Calls

[|<— Back] ^^ Up ^^  [|Next—>][ Finally, function calls. This might already work. Let's write an experiment and see what the results are: code foramt="powershell" @{expression = 'f(g(3))'; expected = @('f', '(', 'g', '(', '3', ')', ')')} code This passes. The question I'm wondering is whether we want those results, or something more like this: code format="powershell" @{expression = 'f(g(3))'; expected = @('f(', 'g(', '3', ')', ')')} code As it turns out, the first version passes as is. The second version requires a change to one of the regular expressions: code format="powershell" static [Array]$regex = @( '^([])', '^([\d\w]+\({0,1})', '^([^\d\w\s]+)' ) code The change is in the middle regex, allowing for zero or 1 ( at the end of a series of digits and letters. Given the change is easy, I'll leave this as is and consider the tokenizer done for now. Next, we'll move on to the Shunting Yard Algorithm in PowerShell 5.

Here's my final-ish version.. [|<— Back] ^^ Up ^^  [|Next—>][