[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: [ANN] LPeg 1.0.1
- From: "Soni L." <fakedme@...>
- Date: Sat, 10 Jun 2017 19:38:31 -0300
On 2017-06-10 07:18 PM, Parke wrote:
It was thus said that the Great Alexander Nasonov once stated:
what bugs were fixed in [LPeg] 1.0.1?
On Sat, Jan 14, 2017 at 6:30 PM, Sean Conner <email@example.com> wrote:
A bug raised in September  that I recently reminded Roberto of .
On Sun, Apr 9, 2017 at 9:03 AM, Patrick Donnelly <firstname.lastname@example.org> wrote:
lpeg = require"lpeg"
local patt = lpeg.Cg(lpeg.Ct"", "foo") * lpeg.Cb "foo" * lpeg.Cb "foo";
table: 0x1926fd0 table: 0x1927010
Doesn't look fixed? Are you referring to some other issue?
The below is my attempt to remove some ambiguity from this old thread.
I suspect Sean's  link is incorrect, and Sean meant to link to this thread:
Subject: [LPeg] intermittent stack exhaustion
Regarding Sean's actual  link, which contains the "issue" mentioned
above by Patrick:
The "issue" is not a bug. In this case, LPeg's behavior is acceptable
and in line with the documentation, as explained by Roberto in the
I, too, have a preference for memoization. I believe Cg should create a
lazy-evaluated-once variable. Would help with RAM usage and GC.
Disclaimer: these emails may be made public at any given time, with or without reason. If you don't agree with this, DO NOT REPLY.