pest VS just

And some related parser tools: - https://github.com/kevinmehall/rust-peg - https://github.com/pest-parser/pest - https://github.com/lalrpop/lalrpop

I had recently completed the first year of my Computer Science class at school and will begin my second year soon. My schools' class forces the use of Java programming language, and I absolutely hated it. So, over the course of a little less than a month, I wrote my own programming language, in Rust (objectively best programming language), using pest, to be as similar to Rust as possible, but compiling to Java.

I second pest.rs. Using it is fairly intuitive and there's also a live playground on their website which is great for quickly developing and testing your AST (abstract syntax tree) parser for whatever language you're implementing.

I’ve been using pest for my own dsl resently. Couldn’t say if it’s state of the art or not, but it is definitely useful. https://pest.rs

Give https://pest.rs a try.

Maybe Pest or Nom for parsing the language.

I haven't written any template engines, but I imagine you'd want to use a proper parser generator like nom, pest, etc. to get the statefulness you need. As the famous StackOverflow answer says, you can't parse a non-regular language with a regular expression... or at least not the kind of "no lookahead/lookbehind" regex engine Rust uses.

But personally I would recommend something like Pest (which is still fairly popular). (Creates)

This was in C, and there it's a pointer arithmetic nightmare. Also, this was before I had any education in writing parsers. These days I'd probably just use a parser generator like pest.

Welp there is absolute chaos in that thread -- guess it's not an April Fools joke.

I wonder if relying on CI for anything other than provisioning machines is a mistake -- maybe we should have never moved from doing things from local scripts written in $LANGUAGE.

That said, I'm probably biased since I'm a massive fan of things like `make` and more appropriately for the current age, `just`[0]

[0]: https://github.com/casey/just

> When a command has some cognitive requirements I create a script with some ${1:-default} values and I store them all in $PATH enabled local/bin

I would consider using just for this:

https://github.com/casey/just

Your coworker's experience is more principled: Make is a mediocre tool for executing commands. It wasn't ever designed for that. Although it is pretty common to see what you are mentioning in projects because it doesn't require installing a dependency.

For a repo where an easy to install (single binary) dependency is a non-issue, consider using just. [1] You get `just -l` where you can see all the command available, the ability to use different languages, and overall simpler command writing.

[1] https://github.com/casey/just

This is fantastic, but I'd say that this solution is somewhat in response to this open issue from 2019:

https://github.com/casey/just/issues/429

I really wish just was included as a package in distributions.

So far, I didn't work on new features at all but on stabilizing the ground for further development: 1. CMake lists and modules were rewritten a lot, now managing builds and their configurations is much lesser pain. 2. Brought in Justfile for regular tasks, and it's great, no less. 3. Linters, formatters, analyzers for almost all the code (except for Janet for now, as because of it being a niche and young technology, it didn't get enough attention yet). 4. ECS stub. Now runtime class doesn't look like a god object. 5. Started writing unit tests which didn't happen with my personal projects before and maybe indicates how serious am I about this one :D 6. Some of previously hardcoded data has been moved to INI files. Now, if I release the game in 10 years, and in 10 more years some eccentric person decides to make a variant of it, it will be slightly simpler.

https://github.com/casey/just - more of a command runner but the Justfile syntax is quite Makefile-like.

If you dislike make checkout just https://github.com/casey/just

i've grown to like this for my personal projects. https://github.com/casey/just

Make is not exactly made for task definition and running, but it can be used like so as long as you know its quirks and counter intuitive gotchas, of which there are many seeing as Make is meant for building sources first and foremost. I use it a lot. I've been meaning to convert at least my personal stuff to https://github.com/casey/just or another task runner for some time though, Make can really be annoying sometimes.

Reminds me of `just`. Which I love.

https://github.com/casey/just