Implementing wc in the language you're writing is a milestone, right?

I was inspired by #uxntal and I'm really grateful for every "how to write an interpreter" blog post I've skimmed over the course of my life. This is fun.

Working on a new #Uxntal book, it seems the "Learn X in Y Minutes" script format was not ideal.

I wat to make something intensive and extensive a "Uxntal Pocket Reference".

So far I have a working Sphinx + Texlive installation that highlights Uxntal syntax correctly, thanks to Python pygments out of the box support for Uxntal! \o/

The image shows the Drifblim acid.tal assembler test:

#uxn #varvara

I'm trying to make a new version of Learn #uxntal in Y minutes, based on the other languages:

https://paste.sr.ht/~ismael-vc/72b446745f60ce160c307ffa598e1d26c1affa1e

This is the current output:

https://paste.sr.ht/~ismael-vc/9e070e14520e9255b03c3bad5a18ee1952fd734e

Any positive feedback is welcome! :)

#uxn #varvara

thinking about dynamic file inclusion in uxntal…

I do not want to implement filename globbing in drifblim

can I delegate this to some shell preprocessor instead?

I have made two "exact" #uxntal syntax highlight definitions, one for Micro and the other for Sublime Text, for their respective default Monokai themes.

I only use these editors, but I plan to make one for vim as well:

https://git.sr.ht/~ismael-vc/monotal/tree

Now my brain doesn't have to notice the highlighting differences when I switch editor.

These will work with any theme in those editors I just made sure both Monokai themes looked the same in both editors.

Sublime Text left, Micro right:

#uxn #varvara

RE: https://mastodon.social/@snufkin_vc/116710615559101382

I made this super simple #uxn REPL library for @wim_v12e but I also post it here in case it is also useful for your #uxntal projects :3

#varvara

Now that I am developing a new #uxn #uxntal assembler in #python, I've been experimenting with a new way 2 do modularity without sacrificing granularity, by preloading macro definitions into D asm dict.

The answer seems to be macros (lots and lots of them) not the concat rune `~`!

This is how the lib would look like:

https://paste.sr.ht/~ismael-vc/cc9e6bc0ea058aa39e19acbeaa8a386df814b752

And this is how it would be used:

https://paste.sr.ht/~ismael-vc/a7c06e08effd6f45254435e60c5a7c1f984dbcf8

The pros is that it is 100% valid uxntal

https://paste.sr.ht/~ismael-vc/424ffda7bee22b1f05610716ee4bc41fddc37b46

What have U come up with?

finally pivoting back towards deluge (sorry network device fans),
i am reminded of just how messy it is…

file includes all over the place! scope definitions based on file paths! method call shorthands! yuck :(

there's some good ideas in there though, maybe i'll add a feature or two to my drifblim fork :D