lexy VS read

lexy (https://lexy.foonathan.net/)

https://github.com/foonathan/lexy nakon sto sam se propatio sa errorima od boost spirita, a pegtl mi se nije svidao, ovaj library je dosao kao odusevljenje, a i dokumentacija je iznenadujuce ok

In general, LALR parser generators are more difficult to work with than RD parser combinators. Instead of flex and bison, I'd recommend checking out Boost.Spirit or lexy.

This might be closer: https://github.com/foonathan/lexy

Lexy: https://lexy.foonathan.net/

lexy has something like std::bind with a way to specify fallback values for the placeholders if the arguments aren't provided: lexy::_1.or_default(fallback)

It was on the mailing list that screens proposals prior to writing papers. Basically it was for making input much easier to work with, like this: https://github.com/ShakaUVM/read

I have thought about submitting a library of mine (https://github.com/ShakaUVM/read) for standardization or inclusion in Boost. Basically it does for input what format did for output - replace the stream system with something more functional.

Using readlib:

That's why I wrote my read library (https://github.com/ShakaUVM/read). You can just do:

5) Make input come from functions rather than call by reference, such as what I did here: https://github.com/ShakaUVM/read