Re: lpeg.Carg() weirdness

[Parke <parke.nexus@...>]

> It was thus said that the Great Parke once stated:
>> On Sat, Jun 24, 2017 at 9:22 PM, Sean Conner <sean@conman.org> wrote:
>> I find the current behavior to be consistent with other parts of Lua
>> that raise an error when the arguments provided to a function are
>> obviously wrong.

On Sat, Jun 24, 2017 at 10:51 PM, Sean Conner <sean@conman.org> wrote:
>   A) there is no obvious value for additional arguments---they can be
> anything, including nil (as I've shown) and B) it's the value meant to be
> used as a capture.

Perhaps I should have said "... that raise an error when the arguments
provided to a function are obviously wrong, including, as in this
case, when the number of arguments provided is obviously wrong."

-Parke