arcsecond VS parser-demo

I've been working pretty hard for the last couple of years to bring a lot of these capabilities to JS/TS. Arcsecond (and it's binary extension) is a general library for parsing, which can easily take a block of memory and convert it to a workable data structure (even when that data structure is some kind of contextual union). You can use construct-js to (re)build an arbitrary byte buffer from structured data, making use of operators for sizeof and pointers.

I basically need what the title says. I found a library called arcsecond that is open sourced and I want to be able to use it in a Google Apps Script environment. The environment supports ES6, so I'd like to compile all of the files into one ES6 Javascript file, with no imports.

Parser combinators are great. I also built and maintain arcsecond, which is a parser combinator library for TypeScript and JavaScript.

It is indeed! I'm planning on adding some parsing capabilities as well (just like in python construct) - but I've actually written a much more general purpose tool for that call arcsecond which allows for defining binary and text parsers declarative.

I have a demo project that fixes a lot of the default insanities.

I have an old demo project that demonstrates most of that for flex/bison, but this is C/C++ oriented so might not be super applicable for you.

It's just unfortunate that flex and bison have bad defaults due to historical compatibility with lex and yacc. If you're using them I have a demo project that tweaks the defaults toward sanity, though I haven't updated it for recent warnings.

I made a demo project that ties them together. I'm pretty sure at least one of the fixes was due to header cycle problems, but I haven't touched it for a while. (note also that the demo was fully warning-clean at the time, but there may be new warnings since)

I made a demo project that avoids several historical annoyances with Flex and Bison - in particular, I made it warnings-clean (though I haven't updated it recently), and I avoid global state.

I have a demo project that enables all of the non-default options that you really should be using in all new projects. Note that the demo doesn't demonstrate meaningful grammars, just shows how to arrange the surrounding code and makefile.

I have a demo project that twiddles most of the important knobs.

Bash is a really complicated language. Redirections and such are simple; they are just tokenization, and any lexer/parser tutorial should get you there (I have a demo project using flex/bison).

Bison can be configured to avoid every single one of those problems. I use reentrant versions (both with and without push parsing) in my demo project. I admit I didn't bother with named references or cleaning up after errors.

a lot of the things that people hate about flex/bison is actually just their defaults for compatibility with lex/yacc, which can be changed. I have a demo project that does some of the things: https://github.com/o11c/parser-demo