Re: There's a bug in my LPeg code, but I can't find it

[Sean Conner <sean@...>]

It was thus said that the Great Albert Chan once stated:
> 
> > On Aug 18, 2018, at 12:44 AM, Sean Conner <sean@conman.org> wrote:
> > 
> >  -spc (And now to debug the problem this change introduces ... [1])
> > 
> > [1]    Namely, an additional segment that's empty, which is technically
> >    correct (I guess?) but I have to think how to handle this ...
> > 
> 
> Again, new segment definition can match anything.
> 
> Thus "status///////////......." will include all the extra "/"

  Yup.  That's what the URL grammar says [1].  It says nothing about how to
deal with multiple slashes like your example.

> Is that what you want ?

  Not really.  But I got past the error I was encountering.

  -spc

[1]	RFC-3968.