lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


2010/2/22 Roberto Ierusalimschy <>:
>> The description of lpeg.Cmt on
>> describes
>> the behaviour when the called function returns a number, false, nil,
>> or no value. If I understand the example "Lua's long strings"
>> correctly, it can return true which does what I would expect: the
>> match is successful.
>> If this is correct, I'd suggest to add this clarification.
> It is correct. The new manual will say that.

Thank you, very fine.

>> BTW: If I'd had to process a rather _large_ string, using lpeg.Cmt
>> would be the adequate tool, because the other options hold the
>> captures in memory until lpeg.match returns, right?
> I missed you here. All kinds of captures must be kept in memory until
> match returns, so that it can return them, no?

Yes, obviously. I should have included a small (nonsense) example to
make it clear:

-- count lines

require 'lpeg'

local N = 0
local function fline()
    N = N + 1
    return true

local crlf  = lpeg.P'\n' + lpeg.P'\r\n'
local line  = -1 + lpeg.Cmt( ( 1 - crlf )^0, fline )
local lines = line * ( crlf * line )^0

lpeg.match( lines, arg[ 1 ] ):read( '*a' ) )
io.stdout:write( N, ' lines\n' )

Clearly, the captured data of lpeg.Cmt has to be in memory as it is
passed to fline(). But can I process a multi million line file this
way or are all the multi million captures kept until lpeg.match() has
returned? It was my hope that the 'clue' of lpeg.Cmt is that I can do

Ok, I still read in the whole file at once, so my memory has to be
that big, at least...