Notices

1. Adrián Pérez (aperezdc@mastodon.social)'s status on Sunday, 14-Nov-2021 12:44:23 CET Adrián Pérez

   • Ekaitz Zárraga 👹
   • Piggo🐽

   @ekaitz_zarraga @piggo same here, I kind of follow the explanations but get quite lost in the assembly, so at some point I started trying to translate things into MIPS assembly... But then life intervened and taking care of a newborn didn't leave much spare time for after work hacking. When/If at some point I get to retake the project, it's going to be RISC-V.

   • Piggo🐽 (piggo@piggo.space)'s status on Sunday, 14-Nov-2021 11:04:05 CET Piggo🐽
     you can test my horrible forth now https://git.ondrovo.com/MightyPork/forth/src/branch/master/src
     
     no rust this time!
     
     it works except there are no control statements yet (IF-ELSE, loops) so it's kinda toothless. but you can recurse. infinitely because no if lol
     
     oh and lot of other stuff is missing too, but you can play with the stack and some arithmetics
   • Piggo🐽 (piggo@piggo.space)'s status on Sunday, 14-Nov-2021 11:04:05 CET Piggo🐽

     in reply to

     • Ekaitz Zárraga 👹
     • Piggo🐽
     @ekaitz_zarraga hey ekaitz so the forth is here! Kinda. see previous post. You wanted to look, now it would be useful 😇
     
     I think I'm going the wrong way about it, so far all was easy sailing, but now there's words like POSTPONE, DOES>, the comma operator and the whole business with variables and values. It's really mudding the boundary between a compiler and interpreter. I also feel like some things were added because it made sense for a particular implementation of the runtime, like assuming there is something called "dictionary pointer" just pointing into a block of bytes... there's a lot of unanswered questions with the spec, like eg where should a string used in a compiled word reside, .. where the compiled words themselves (the bytecode) actually should go ...
   • Adrián Pérez (aperezdc@mastodon.social)'s status on Sunday, 14-Nov-2021 11:04:05 CET Adrián Pérez

     in reply to

     • Ekaitz Zárraga 👹
     • Piggo🐽

     @piggo @ekaitz_zarraga the most understandable Forth I have found so far, which explains in the comments how many concepts are mapped to actually (low level) implementation is Jonesforth: https://github.com/nornagon/jonesforth — maybe that helps?

   • Adrián Pérez (aperezdc@mastodon.social)'s status on Sunday, 14-Nov-2021 12:37:26 CET Adrián Pérez

     • Ekaitz Zárraga 👹
     • Piggo🐽

     @ekaitz_zarraga @piggo you mean “crazy bad”, “crazy cool”, or “batshit insane crazy”?

     Or... Maybe all the crazies at the same time? :blobpeek:

   • Adrián Pérez (aperezdc@mastodon.social)'s status on Sunday, 14-Nov-2021 12:54:43 CET Adrián Pérez

     in reply to

     • Ekaitz Zárraga 👹
     • Piggo🐽

     @ekaitz_zarraga @piggo ultimate goal: make it independent enough from syscalls that it would run in any machine where SBI console functions can be used as input/output.