On Mon, Jan 9, 2023 at 9:13 PM Glauco <[email protected]> wrote:
> > The grammar created (for my local set.mm file) has 1624 rules (but 3
>> are for working vars), so I'm pretty sure, Nearly.js has no problem with
>> large-ish grammars.
>>
>> No, it's the size of the file it's parsing, not the size of the grammar,
>> that I'm saying may be problematic.
>>
>
> Is it problematic in time or in space? (for what I read, if you can
> express the grammar left-recursively, even early parsers should be linear
> in time)
>
Space. Sorry for the late answer but I couldn't be entirely certain it
wasn't both, because running out of memory can be a time consuming
business. But when I set up my parser to generate an empty parse tree it
zipped over set.mm in an eyeblink. Hopefully the problems were just down
to bugs in my code and an inefficient parse tree. It was dragging me down
for a while but after this insight a couple of nights ago I feel like I'm
winning with this problem once again.
Best regards,
Antony
--
You received this message because you are subscribed to the Google Groups
"Metamath" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/metamath/CAJ48g%2BAOK4Q_KgbQJvrYZw4Obp5H%3DfvF3%3D78b-6JgtLoj0TQ9A%40mail.gmail.com.
