[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: There's a bug in my LPeg code, but I can't find it
- From: Albert Chan <albertmcchan@...>
- Date: Sat, 18 Aug 2018 06:45:25 -0400
> 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 "/"
Is that what you want ?
- References:
- There's a bug in my LPeg code, but I can't find it, Sean Conner
- Re: There's a bug in my LPeg code, but I can't find it, Daurnimator
- Re: There's a bug in my LPeg code, but I can't find it, Daurnimator
- Re: There's a bug in my LPeg code, but I can't find it, Sean Conner
- Re: There's a bug in my LPeg code, but I can't find it, Daurnimator
- Re: There's a bug in my LPeg code, but I can't find it, Sean Conner
