Lisp macros.
But I'd be curious of the possibilities of generating code with tree sitter.
this post was submitted on 28 Mar 2024
17 points (90.5% liked)
Programming
17378 readers
585 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Never tried lisp, it's always been on my "as soon as I have an excuse to learn it" list (alongside haskell). What makes it adapted to this use case?
For this problem I'd usually go python + jinja but I cannot say I like the experience.
Both languages you mentioned i highly recommend.
Lisp macros are another level, because they are part of the language - you can use all language primitives to transform forms however you like.
Haskell will give you a different view of programming. It's beautiful and concise, and implements all sorts of academic research in languages. Ocaml is similar in many respects.
Just thought of an example. If you want to, you can open a file at macroexpansion time, and generate code based on its contents. There are no limits, pretty much.
I've never needed to use a template processor to generate code. Usually a macro system built into the programming language is better for this. I think template processors are more commonly used for generating text documents.
What problem are you trying to solve?
The most common usecase is generating data models based on the database, mostly using t4 files so far. We have a non-standard way of defining some parts of it so the default MS tools don't quite cut it (like ef dbcontext scaffold). I've been looking into roslyn but it seems like it might be more trouble than its worth, but default t4 doesn't even have a proper editor and syntax highlighting so its a low bar atm.
If you're writing C#, you could take a look into Source Generators. They're supported directly by Roslyn I believe, and are pure C# instead of t4's syntax. They're often used with attributes to augment types, but I believe they can be used to generate sources on their own, and even read from a config file if you want to (or maybe even query the DB, if that's something you want to do at build time for some reason, though I've never tried this).
Is it prohibitively expensive to manually define your data types? How many do you have?
I do not generally recommend using ORMs, but this advice is likely dependent on the particular ecosystem you are dealing with.
It seems like you are pretty deep into Microsoft/.NET territory. I don't have any experience with .NET so I might not be the best person to help.
T4, small scripts, text search and replace, multicursor editing if that counts, dotnet code generators
Preference depends on the context.
"Modify" isn't really generating though, so I'm not sure whether your question is clear (to me).
For simple snippets like templates I'm using Obsidian and Obsidian Templater ( - For any programmer I'd consider Obsidian the best note-taking-app by miles.)
For more complicated stuff I used to just build generators in code, but as you mentioned, that's kind of a nightmare to manage. So now I usually use Liquid Templates - and a custom parser I made to process them
Have you looked into snippets?
I use Nix. Or, rather, I use traditional tools like sed and awk and python, along with newer tools like jq so that I can store tables in JSON, and I call those tools from Nix builders. For example, this flake builds a book in several stages, starting by generating DOT from diagrams, then feeding some JSON tables via jq into Python scripts (replacing older awk scripts) to generate some Markdown tables and Metamath axioms, and finally calling mdbook and metamath to build the HTML for the book.
I don't really do that - I tend to aggressively refactor code. This is, I admit, a privilege of being a highly trusted developer at my company.