TX-2-simulator VS nom

Source code

You could implement some opcodes at https://github.com/TX-2/TX-2-simulator

Thanks to /u/TGSCrust I've got things working now. In case anybody else is interested in this, I now have a complete working example.

I've been working on an assembler and right now it uses nom. While nom isn't great for error messages, good error messages will be important for this particular assembler (current code), so I've been attempting to use the methods described by Eyal Kalderon in Error recovery with parser combinators (using nom).

Here's an example of a tape loader program from a very fancy machine, the TX-2. The TX-2 was fancy in a lot of ways, but most relevantly here because the tape loader code was set up permanently on a plugboard instead of having to be toggled in at boot time. The TX-2 is interesting and important because it was the machine that Ivan Sutherland's Sketchpad ran on.

https://github.com/TX-2/TX-2-simulator is written in a combination of Rust and Typescript. It's not finished yet, and the UI needs lots of improvement.

https://github.com/TX-2/TX-2-simulator could really use some help

This github workflow builds this project and deploys it to the gh-pages branch of this project whose main branch isn't interesting.

If you're interested, please take a look at the TX-2 project's website and, if you like, the source code. If you haven't eaten in the last hour or so, you might also find it interesting to take a look at the online demo. There's a collection of "good first issue" items too.

TX-2 (code)

Just in case you are not familiar with nom, it is a parser combinator written in Rust. The most basic thing you can do with it is import one of its parsing functions, give it some byte or string input and then get a Result as output with the parsed value and the rest of the input or an error if the parser failed. tag for example is used to recognize literal character/byte sequences.

I may be the only one not familiar, but nom refers to https://github.com/rust-bakery/nom which looks like a pretty handy way to parse binary data in Rust.

Lots of people use nom for their parsing needs, but that's not the only game in town and there other options.

As much as I love nom as well as other parser combinator libraries, regex-based parsers, BNF/EBNF-based parsers, etc. I always end up going back to plain old text-based char-by-char scanners.

I am using nom / nom_locate to build the parser side because I've done a handful of other projects with it, and I plan to use tower-lsp to hook up the language server side.

Look into a parsing library such as https://github.com/rust-bakery/nom

If we were in /r/learnrust I'd have recommended the nom crate for this.

Thanks to the flexibility of [nom](https://github.com/rust-bakery/nom), it is very easy to write your own parser in rust, read [this article](https://github.com/metaworm/luac-parser-rs/wiki/Write-custom-luac-parser) to learn how to write a luac parser

I've been working on an assembler and right now it uses nom. While nom isn't great for error messages, good error messages will be important for this particular assembler (current code), so I've been attempting to use the methods described by Eyal Kalderon in Error recovery with parser combinators (using nom).