vipak and toml package description local build

https://toobnix.org/w/nCF2kFnEro6kxNMeUx9Ave

Weekend fun coding the beginnings of an exhaust fan controller using the programming language #oberon (07) targeting (bare metal -- no Arduino, no C libs) #AVR (avr128db48) using #plan9 ports #acmeEditor on a MacBook Pro.

Can I get more obscure than this?

Oh wow.

Cross-module calls are working!

Next up: c-ffi.

#oberon #compiler #llvm

So I'm writing a #compiler. No LLMs just my squishy brain and textbooks for the language #Oberon and docs for #llvm

This is a path well travelled but my trick is I'm keeping Professor Wirth's freely licensed original source and replacing only the code generation parts with calls to the llvm-c api.

So I guess I'm not even writing the compiler, I'm adapting it.

Huge thanks to obnc which translates oberon to c. When the translated compiler can compile itself I'll just stop using the translator.

Niklaus Wirth and Chuck Moore had a lot more in common than I ever expected to discover.

I've known about both since the early 1980s (Wirth via using USCD and DEC20 Pascal and Moore via various #Forth implementations I used on the Commodore 64).
They seem to be worlds apart, but both:
1. Worked towards simplicity in its purest (but practical) forms
2. Designed their own hardware and programmed them bottom up in their own programming languages.
3. Took more and more away from their languages (stripping down to their bare essentials)

I'm currently hacking using Wirth's #oberon language (target compiling for 8-bit AVR) and the restricted language features of oberon is forcing me to think "differently" in similar ways that #forth does.