From Devine Lu Linvega to ~vdupras/duskos-discuss
I'm starting to wonder if maybe I shouldn't start adding forth syntax-highlight to Left now that you're nearing having Varvara up and running. Is there anything at all you'd like me to prepare in advance? My guess is that you're aiming for screen.tal, mandelbrot.tal, picture drawing examples that make use of the filesystem, polycat.tal and controller.tal for input, and by that point Left should be usable - And Dusk modifiable from within itself. So, if there's anything that you think you'll need to make this easier, let me know and I'll get right to it.
From Devine Lu Linvega to ~rabbits/uxn
Hey everyone, From time to time, someone asks if there's something like Uxn32's debugger planned for the other emulators, and since we can't quite all agree on the API needed to make this happened, I went ahead and wrote a uxn emulator, in uxn itself. source: https://git.sr.ht/~rabbits/beetbug/tree/main/item/src/emulator.tal This allows anyone to step through their program and follow the stack states and follow the PC around, it's totally portable, it doesn't make use of any special System port. I'm sure there's still some improvements to be made for it, but I've used it today to step through a bunch of routines I was implementing and it delivered.
From Devine Lu Linvega to ~rabbits/public-inbox
Hey everyone, From time to time, someone asks if there's something like Uxn32's debugger planned for the other emulators, and since we can't quite all agree on the API needed to make this happened, I went ahead and wrote a uxn emulator, in uxn itself. source: https://git.sr.ht/~rabbits/beetbug/tree/main/item/src/emulator.tal This allows anyone to step through their program and follow the stack states and follow the PC around, it's totally portable, it doesn't make use of any special System port. I'm sure there's still some improvements to be made for it, but I've used it today to step through a bunch of routines I was implementing and it delivered.
From Devine Lu Linvega to ~rabbits/uxn
Hi everyone, I'd like to follow up on that thread with a link to the documentation for the metadata standard, for anyone stumbling on this link in the future: https://wiki.xxiivv.com/site/metadata.html I've also made a little graphical utility to test metadata https://git.sr.ht/~rabbits/uxn/tree/main/item/projects/utils/metadata.tal If you want to add metadata, but don't have the space or need to store a whole 64x64 icon, use =ffff as address for the app icon.
From Devine Lu Linvega to ~rabbits/uxn
Hello everyone, Long time no talk, I had a question and I'd like your opinion. binarycat needed raw byte values for their project, and I did a quick scan of some of my own projects and found a good couple of .zplabel STH, which should really be more like LITr -zplabel So I was thinking, what would you say if on top of : for raw label shorts, I added =label for raw shorts, and -label for raw bytes? Consider your macros that might begin with - or =. Let me know what you think :) Dll
From Devine Lu Linvega to ~rabbits/public-inbox
Thanks :)
From Devine Lu Linvega to ~rabbits/uxn
Hi all! I've been working on this Uxntal operating system for the better part of the past few days, and I started noticing that things were kind of weird, and that building without tail-call optimisations resolved the issue, the project is massive and I couldn't for the life of me, figure out where the optimisation issue was occurring. https://git.sr.ht/~rabbits/potato/commit/8323c42390821050418503bfd823aba17dd821b4 So yeah, be careful out there, I'll try to weed out the bug and figure out which part fails. Just a head's up :) Have a good rest of summer
From Devine Lu Linvega to ~rabbits/uxn
This is specifically for Felix, but I'd like to make this conversation available to all, in case anyone has ideas. In UF, when uxncli under/overflows, it breaks the repl. It'd be nice to agree on a way to handle this stuff by using this as a usecase. The way I would handle this is to set a System/vector and clean up the stack in that vector, and throw a custom error. Do you think that would work for you? We could make that behaviour standard across emulators if that would do it? What would be the ideal UX to handle that?
From Devine Lu Linvega to ~rabbits/uxn
I've implemented a simple check using a device support bitmask at the emulator level, it'll catch 90% of the incompatibility issues which will likely be folks trying to run graphical roms with uxncli. The report came from someone using uxn11 on BSD, but this should probably be added to uxnsdl as well. https://git.sr.ht/~rabbits/uxn11/commit/5d837313e56d19cd6ecfa2ad9746edca20afb5f6
From Devine Lu Linvega to ~rabbits/uxn
Found an exception. The file device is a bit tricky I suppose, for example, noodle doesn't assign a File/name until it tries to save, but the device does have a vector, although it is unused. Maybe applications should still test available devices on reset, I could set a #0000 to File/vector on reset to make sure that it is available. If all else fails, a bit mask in a byte might work, but let's try to see if we can do without first.