[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison lexer
From: |
Frank Heckenbach |
Subject: |
Re: Bison lexer |
Date: |
Sat, 01 Sep 2018 00:12:27 +0200 |
Hans Åberg wrote:
> > I haven't used gcc-8 yet, but how is this relevant? If anything, I
> > expect newer gcc versions to produce more warnings (usually useful)
> > which flex might also suffer from.
>
> Maybe the Flex lexers errors is due to using C89 to compile it or something.
No, the warnings seemed legit.
> > Interesting, thanks. Fortunately, my REs are not so complex, so the
> > bug you reported won't affect me and lexing speed is not so
> > important for me, so (at least for now) I can just use the library
> > as is. But if I ever need something more sophisticated, I'll keep
> > this in mind.
>
> If that is what you are using, note that it is recursive, so the function
> stack might overflow. But perhaps the rewrite it someday.
I don't think my lexing REs should cause much recursion. No nested
repetitions or such.
Regards,
Frank
- Re: Bison C++ mid-rule value lost with variants, Akim Demaille, 2018/08/12
- Re: Bison C++ mid-rule value lost with variants, Frank Heckenbach, 2018/08/26
- Re: Bison C++ mid-rule value lost with variants, Akim Demaille, 2018/08/27
- Re: Bison C++ mid-rule value lost with variants, Hans Åberg, 2018/08/27
- Re: Bison C++ mid-rule value lost with variants, Frank Heckenbach, 2018/08/28
- Bison lexer, Hans Åberg, 2018/08/29
- Re: Bison lexer, Frank Heckenbach, 2018/08/31
- Re: Bison lexer, Hans Åberg, 2018/08/31
- Re: Bison lexer,
Frank Heckenbach <=
- Re: Bison lexer, Hans Åberg, 2018/08/31
- Re: Bison C++ mid-rule value lost with variants, Frank Heckenbach, 2018/08/28