home.social

#varvara — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #varvara, aggregated by home.social.

  1. hexdump -C needed a spa day, so I gave it a massage:

    paste.sr.ht/~ismael-vc/a074bf4

    :3 #uxn #uxntal #varvara

    Though I'm making my hexdump a tool that can be passed a ROM file as an argument (it was inspired by hexdump -C), it is nice to see that with a little effort is doable as well with the existing tools.

    I also bought the awk pocket reference, so useful.

    (If there is a better way to do this with awk, I'd love to learn!)

  2. hexdump -C needed a spa day, so I gave it a massage:

    paste.sr.ht/~ismael-vc/a074bf4

    :3 #uxn #uxntal #varvara

    Though I'm making my hexdump a tool that can be passed a ROM file as an argument (it was inspired by hexdump -C), it is nice to see that with a little effort is doable as well with the existing tools.

    I also bought the awk pocket reference, so useful.

    (If there is a better way to do this with awk, I'd love to learn!)

  3. hexdump -C needed a spa day, so I gave it a massage:

    paste.sr.ht/~ismael-vc/a074bf4

    :3 #uxn #uxntal #varvara

    Though I'm making my hexdump a tool that can be passed a ROM file as an argument (it was inspired by hexdump -C), it is nice to see that with a little effort is doable as well with the existing tools.

    I also bought the awk pocket reference, so useful.

    (If there is a better way to do this with awk, I'd love to learn!)

  4. hexdump -C needed a spa day, so I gave it a massage:

    paste.sr.ht/~ismael-vc/a074bf4

    :3 #uxn #uxntal #varvara

    Though I'm making my hexdump a tool that can be passed a ROM file as an argument (it was inspired by hexdump -C), it is nice to see that with a little effort is doable as well with the existing tools.

    I also bought the awk pocket reference, so useful.

    (If there is a better way to do this with awk, I'd love to learn!)

  5. I made an article at #Uxnomicon documenting the API of Zen, my tny #Uxntal testing framework:

    uxnomicon.miraheze.org/wiki/Ze

    I hope it might be helpful for others as it has been to me!

    : )

    #uxn #varvara #TDD

  6. I made an article at #Uxnomicon documenting the API of Zen, my tny #Uxntal testing framework:

    uxnomicon.miraheze.org/wiki/Ze

    I hope it might be helpful for others as it has been to me!

    : )

    #uxn #varvara #TDD

  7. I made an article at #Uxnomicon documenting the API of Zen, my tny #Uxntal testing framework:

    uxnomicon.miraheze.org/wiki/Ze

    I hope it might be helpful for others as it has been to me!

    : )

    #uxn #varvara #TDD

  8. I made an article at #Uxnomicon documenting the API of Zen, my tny #Uxntal testing framework:

    uxnomicon.miraheze.org/wiki/Ze

    I hope it might be helpful for others as it has been to me!

    : )

    #uxn #varvara #TDD

  9. #Uxntal #testing #framework in 760 bytes.

    paste.sr.ht/~ismael-vc/2f2d41f

    I have called it Zental, in the images you can see it testing itself (the failed tests are expected).

    Usage: paste.sr.ht/~ismael-vc/82d44be

    Just create a routine under the @ test scope, ie:

    @ test/foo ( -> )
    /verbose
    { "some 20 "set } /set
    { "some 20 "subset } /subset
    #01 #0101 EQU /assert
    /end-subset
    /end-set
    /summary
    BRK

    ~zen.tal

    I'll put it in a repo soon. :3

    #uxn #varvara #TDD

  10. #Uxntal #testing #framework in 760 bytes.

    paste.sr.ht/~ismael-vc/2f2d41f

    I have called it Zental, in the images you can see it testing itself (the failed tests are expected).

    Usage: paste.sr.ht/~ismael-vc/82d44be

    Just create a routine under the @ test scope, ie:

    @ test/foo ( -> )
    /verbose
    { "some 20 "set } /set
    { "some 20 "subset } /subset
    #01 #0101 EQU /assert
    /end-subset
    /end-set
    /summary
    BRK

    ~zen.tal

    I'll put it in a repo soon. :3

    #uxn #varvara #TDD

  11. #Uxntal #testing #framework in 760 bytes.

    paste.sr.ht/~ismael-vc/2f2d41f

    I have called it Zental, in the images you can see it testing itself (the failed tests are expected).

    Usage: paste.sr.ht/~ismael-vc/82d44be

    Just create a routine under the @ test scope, ie:

    @ test/foo ( -> )
    /verbose
    { "some 20 "set } /set
    { "some 20 "subset } /subset
    #01 #0101 EQU /assert
    /end-subset
    /end-set
    /summary
    BRK

    ~zen.tal

    I'll put it in a repo soon. :3

    #uxn #varvara #TDD

  12. #Uxntal #testing #framework in 760 bytes.

    paste.sr.ht/~ismael-vc/2f2d41f

    I have called it Zental, in the images you can see it testing itself (the failed tests are expected).

    Usage: paste.sr.ht/~ismael-vc/82d44be

    Just create a routine under the @ test scope, ie:

    @ test/foo ( -> )
    /verbose
    { "some 20 "set } /set
    { "some 20 "subset } /subset
    #01 #0101 EQU /assert
    /end-subset
    /end-set
    /summary
    BRK

    ~zen.tal

    I'll put it in a repo soon. :3

    #uxn #varvara #TDD

  13. Today I have implemented malloc in 76 bytes in #Uxntal .

    paste.sr.ht/~ismael-vc/21de76c

    After fiddling with this all afternoon, I finally have implemented a malloc other than the simple "bump pointer allocator" I was using.

    I'll work on mfree, but that will be for tomorrow.

    I changed the unit size to byte instead of 64 bytes because there is no MMU expecting it in 64 bytes in #Uxn as it was in the PDP, so it makes no sense in Uxn? might bite me later.

    Catmon was indispensable.

    #varvara #unix #pdp

  14. Today I have implemented malloc in 76 bytes in #Uxntal .

    paste.sr.ht/~ismael-vc/21de76c

    After fiddling with this all afternoon, I finally have implemented a malloc other than the simple "bump pointer allocator" I was using.

    I'll work on mfree, but that will be for tomorrow.

    I changed the unit size to byte instead of 64 bytes because there is no MMU expecting it in 64 bytes in #Uxn as it was in the PDP, so it makes no sense in Uxn? might bite me later.

    Catmon was indispensable.

    #varvara #unix #pdp

  15. Today I have implemented malloc in 76 bytes in #Uxntal .

    paste.sr.ht/~ismael-vc/21de76c

    After fiddling with this all afternoon, I finally have implemented a malloc other than the simple "bump pointer allocator" I was using.

    I'll work on mfree, but that will be for tomorrow.

    I changed the unit size to byte instead of 64 bytes because there is no MMU expecting it in 64 bytes in #Uxn as it was in the PDP, so it makes no sense in Uxn? might bite me later.

    Catmon was indispensable.

    #varvara #unix #pdp

  16. Uxnomicon now has support for the Monotal (Monokai for Uxntal) light and dark themes!

    - git.sr.ht/~ismael-vc/monotal
    - uxnomicon.miraheze.org/wiki/Me
    - uxnomicon.miraheze.org/wiki/Me

    The site will respond to your user preferences, if set to auto it changes theme according to your OS theme, else you can manually toggle it using the eye glasses icon (appearance).

    Syntax test page: uxnomicon.miraheze.org/wiki/Ac

    #uxn #uxntal #varvara #monokai #wikimedia

  17. Light and Dark Monokai Theme for #Uxntal in SourceHut.

    It uses one user script and one user css style sheet.

    I like the Terminus font, but you can change it for your favorite, and of course the colors, font size and line spacing as well.

    git.sr.ht/~ismael-vc/monotal/t

    This is running in Linux, Firefox using the Stylus and ViolentMonkey plugins. I'll make a setup guide shortly.

    It will automatically update the theme as I change the OS wide theme.

    Still doing some last tweaks : )

    #uxn #varvara

  18. I found the way to get an absolute reference out of a relative one the other day in #uxn , but what happens if the byte offset is to far away?

    _foo $100 @ foo

    Error: foo too far!

    The following 4 bytes do the trick this time

    %:patch ( [JSI] -- [LIT2] ) { [ LIT2 LIT2 00 ] STR }

    :patch foo ( rel* )

    This in combo with the previous setup allows more room to make relocatable AOT assembled libraries that are easy to include or copy paste.

    Sorry for abusing the < > overload. :P

    #uxntal #varvara

  19. I worked today in #uxn syntax files and I got a consistent style across the micro editor, sublime text and pygments!

    git.sr.ht/~ismael-vc/monotal

    There are instructions on how to use them in the readme.

    Pink: Opcodes
    Orange: % ~ (bold, italic)
    Yellow: | $
    Green: # "
    Cyan: @ & (bold)
    Purple: . , ; - _ =
    Gray: ( ) [ ] (italic)
    White/Black: { } foo /foo !foo ?foo 00
    Cream/Dark Grey: background
    Light Grey: highlight

    Monotal is just how each uxntal token is mapped to a Monokai color.

    #uxntal #varvara

  20. I have updated my #Uxntal syntax definitions for #micro and #subl Sublime Text, as well as #Python #Pygments

    git.sr.ht/~ismael-vc/monotal

    What I want is consistency in the coloring of the uxntal tokens, this is not about the color palette precisely.

    I'm making a book using Pygments and #Sphinx that will use these.

    Sublime Text and Pygments are using the Monokai Pro theme colors.

    Micro is using it's default Monokai theme.

    But you can see all tokens are consistently themed.

    : )

    #uxn #varvara

  21. I have updated my #Uxntal syntax definitions for #micro and #subl Sublime Text, as well as #Python #Pygments

    git.sr.ht/~ismael-vc/monotal

    What I want is consistency in the coloring of the uxntal tokens, this is not about the color palette precisely.

    I'm making a book using Pygments and #Sphinx that will use these.

    Sublime Text and Pygments are using the Monokai Pro theme colors.

    Micro is using it's default Monokai theme.

    But you can see all tokens are consistently themed.

    : )

    #uxn #varvara

  22. I have updated my #Uxntal syntax definitions for #micro and #subl Sublime Text, as well as #Python #Pygments

    git.sr.ht/~ismael-vc/monotal

    What I want is consistency in the coloring of the uxntal tokens, this is not about the color palette precisely.

    I'm making a book using Pygments and #Sphinx that will use these.

    Sublime Text and Pygments are using the Monokai Pro theme colors.

    Micro is using it's default Monokai theme.

    But you can see all tokens are consistently themed.

    : )

    #uxn #varvara

  23. I have updated my #Uxntal syntax definitions for #micro and #subl Sublime Text, as well as #Python #Pygments

    git.sr.ht/~ismael-vc/monotal

    What I want is consistency in the coloring of the uxntal tokens, this is not about the color palette precisely.

    I'm making a book using Pygments and #Sphinx that will use these.

    Sublime Text and Pygments are using the Monokai Pro theme colors.

    Micro is using it's default Monokai theme.

    But you can see all tokens are consistently themed.

    : )

    #uxn #varvara

  24. If you ever need a relocatable #Uxntal routine's byte code (not the source but the ASCII hexdump), yet your code needs to embed an absolute address, ie. in system expansion commands or device vectors.

    This will do the trick

    %:PC ( -- pc+3* ) { [ LITr 00 JSRr ] }
    |9 @ offset2>>
    %<< ( -- offset* 0 ) { :PC ;offset2>> ADD2 #00 }
    %>> ( offset* 0 rel -- abs* ) { ADD2 }

    [
    @ foo ( -- )
    ( ... )
    << ,on-console >> .Console/vector DEO2
    ( ... )
    JMP2r

    @ on-console ( -> )
    ( ... )
    BRK
    ]

    #uxn #varvara 3 : )

  25. If you ever need a relocatable #Uxntal routine's byte code (not the source but the ASCII hexdump), yet your code needs to embed an absolute address, ie. in system expansion commands or device vectors.

    This will do the trick

    %:PC ( -- pc+3* ) { [ LITr 00 JSRr ] }
    |9 @ offset2>>
    %<< ( -- offset* 0 ) { :PC ;offset2>> ADD2 #00 }
    %>> ( offset* 0 rel -- abs* ) { ADD2 }

    [
    @ foo ( -- )
    ( ... )
    << ,on-console >> .Console/vector DEO2
    ( ... )
    JMP2r

    @ on-console ( -> )
    ( ... )
    BRK
    ]

    #uxn #varvara 3 : )

  26. Does anyone have a better way to convert a relative address to an absolute address generically for relocatable libraries?

    This is how I define it, currently using 2 macros

    git.sr.ht/~ismael-vc/software-

    (relocatable in the sense the preassembled text bytecode can be relocated not the source code!)

    This is how I use it:

    git.sr.ht/~ismael-vc/software-

    ( save abs addr of /+dst in /dst )
    << ,/+dst >> ,/dst STR2

    ( pass abs addr of /cmd to expansion )
    << ,/cmd >> .System/expansion DEO2

    #uxn #uxntal #varvara

  27. I have a plan to make #Uxntal tutorials for people from other programming languages.

    Since I don't have much time for planning, starting now, I'll be dumping examples, exercises, etc. as they pique my interest and later I'll order them.

    So I'll start with log/mem in uxntal and log_mem in python:

    uxnomicon.miraheze.org/wiki/Ux

    They even have the exact same bug!
    Can you find it? ; P

    I'm working on fixing it and making log/mem accept a length to dump and an extended ram bank as well.

    #uxn #varvara

  28. Hey y'all! Does this looks uxny enough?

    I want to do a uxnsay cli tool

    $ uxncli fortune.rom | uxncli uxnsay.rom
    $ uxncli echo.rom Hello World | uxncli uxnsay.rom

    Would you help me make an ASCII art Uxn? :3

    I wanted to use ^^ for it's feet but it looks like a cat lol XD

    #uxn #uxntal #varvara

  29. I updated the fortune tool in #Uxntal , with more variation, got one liners with less than 33 cols from the BSD fortunes:

    uxnomicon.miraheze.org/wiki/Fu

    Raw code:

    paste.sr.ht/blob/858668a4a33da

    $ wget -O fortune.tal <rawlink>
    $ uxncli drifblim.rom fortune.tal fortune.rom
    Assembled fortune.rom in 11660 bytes.
    $ cp fortune.rom ~/roms
    $ echo "uxncli ~/roms/fortune.rom" >> ~/.zshrc
    $ source ~/.zshrc

    Or with an alias but check not to clash with BSD's `fortune`.

    I hope it makes you smile : )

    #uxn #varvara

  30. @rl_dane @mdc I wonder how #uxn opcodes compare to what F18 chips from #GreenArrays have.

    Only 32 opcodes, 8 of them special (can be used in th last 3 bits of a kind of 18-bit #VLIW word) versus 256 opcodes of #uxn

    #varvara offers much more high level i/o, F18A has 4 interchip ports, GPIO, A/D interface and SERDES, which can be used to build things like Ethernet for example.
    varvara-fpga does not implement most varvara I/O features at all.

    greenarraychips.com/home/docum

    greenarraychips.com/home/docum

  31. Good evening, and welcome to Uxn News Today!

    In our top story, Angelwood has just announced an exciting new project on Discord: an uxntal #barcode generator!

    This innovative tool, designed for the Uxn ecosystem, is now available for exploration.

    You can check it out at git.sr.ht/~angelwood/upca-uxn. Stay tuned for more updates on this development, and join the conversation with hashtags #uxn, #uxntal and #varvara.

    That’s all for now—back to you!

  32. I am very aware of the #uxn and #Varvara stack machines, and have looked closely at them. Lots of software applications. The reason I did not take that path, is that they are optimised for 8/16 bit CPUs. The #J1 / #MecrispIce family is much better optimised for FPGAs.
    @AlgoCompSynth

  33. I like , but I miss the possibility for interactivity.

    What if we took and made it streamable over the internet. Instead of downloading web pages (with dozens of megabytes of bloated junk), your browser simply downloaded a app that interacted locally. It could be given write access to its own isolated directory, and maybe read access to a specified url (for reading plain text from the internet, in order to be able to present more than 64k of content to the user)?