zeptoforth
hylo
Our great sponsors
zeptoforth | hylo | |
---|---|---|
12 | 54 | |
157 | 1,106 | |
- | 2.9% | |
9.8 | 9.9 | |
19 days ago | 1 day ago | |
Forth | Swift | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zeptoforth
-
Berry is a ultra-lightweight dynamically typed embedded scripting language
microcontroller options are interesting, also Forths (https://github.com/tabemann/zeptoforth)
-
zeptoforth 1.0.0 is out! (Now with optional USB CDC support for the RP2040)
Patch-level release 1.0.1 is out. This release improves the disassembler, particularly adding the ability to properly disassemble string literals.
-
I'm wondering why so few forth microcontoller tutorials are out there?
This is a definite shameless plug, but I would recommend my zeptoforth - it has strong support for the RP2040 (e.g. the RPi Pico), including peripheral support and support for executing on both cores, and also has support for a number of STM32 platforms, and comes with a range of example code, documentation, and a wiki.
-
zeptoforth 0.45.0 out including SDHC/SDXC and FAT32 support
The release itself is at https://github.com/tabemann/zeptoforth/releases/tag/v0.45.0
-
Open Source Forth Systems With First Class Preemptive Multitasking?
Zeptoforth has this, but it’s for embedded systems. https://github.com/tabemann/zeptoforth
-
Modules in zeptoforth
I initially implemented a rather Forth 2012-like wordlist system based on GET-ORDER, SET-ORDER, GET-CURRENT, SET-CURRENT, and WORDLIST for my Cortex-M Forth, zeptoforth. However, I ended up finding these quite cumbersome and error-prone to use in code that makes heavy use of wordlists to control the namespace, as is the case with zeptoforth. As a result I decided to completely remodel wordlists into a module system which, while internally based on those five words, is outwardly much more like the module systems found in other languages.
-
Multicore multitasking for the RP2040 with zeptoforth
Multicore support for the RP2040 with zeptoforth has been in the works for a while but up until the last few days has not been mature enough for me to even consider including it in the devel branch of zeptoforth. However, now it has reached the point where I can run multiple tasks simultaneously on separate cores. I have a working test that blinks the LED on the Raspberry Pi Pico at two different rates in two different tasks, one on each core, while simultaneously writing an asterisk to the console once every second from the second core and having a usable REPL in the main task on the first core. It should be noted that even the Micropython does not do this, as it only allows two tasks, one per core, rather than allowing multiple tasks to run on each core separately.
-
which forth do you guys use for normal day to day scripting and programming
I am the developer of zeptoforth, which is the main Forth I am using at the present. It supports the RP2040 (particularly the Raspberry Pi Pico, but it should work on other RP2040 boards), which I have been working with lately, and the STM32F407, STM32L476, and STM32F746 DISCOVERY boards. Note that it is not a desktop Forth; for that I would probably just recommend gforth.
-
zeptoforth 0.21.0 is out, now with RP2040 support!
zeptoforth 0.21.0 (https://github.com/tabemann/zeptoforth/releases/tag/v0.21.0) is now out, and introduces support for the RP2040 microcontroller (e.g. Raspberry Pi Pico, any RP2040 board with Winbond Quad SPI flash should work). Note that it comes in UF2 format, so one codes not need to solder pins for SWD onto one's Raspberry Pi Pico format to load it, and also the Makefile automatically generates UF2 files. Furthermore, when said UF2 file is first loaded, it erases flash above it up to the 1 MB mark, so one does not need to use OpenOCD (with SWD) or a special eraser UF2 file to clear old code out of flash.
-
Why Forth?
The result of this is zeptoforth, which I have been developing for about a year and four months. One could say that it fits the same niche as Mecrisp-Stellaris, and it admittedly supports far fewer MCU's at the present. I could have just used that rather than bothered to implement my own Cortex-M Forth, but I wanted to create my own Forth environment which I could play with as I saw fit (e.g. adding preemptive multitasking and other multitasking supports such as locks and channels).
hylo
-
Vala Programming Language
Or Val[0], now called Hylo (for a good reason), or V[1].
[0] https://www.hylo-lang.org
-
Cpp2 and cppfront – An experimental 'C++ syntax 2' and its first compiler
The evolution of C++ has been a multi-decade history of dealing with difficult reality.
I have great hope that Herb can create with his cppfront project “The Very Best of C++” to carry that tremendous legacy forward.
If I was to throw my hat into a “C++ successor”, it would be https://www.hylo-lang.org/ with its “all the safeties” and “tell you when you’re doing it sub-optimal” approach.
-
Borrow Checking Hylo [video]
Paper: https://2023.splashcon.org/details/iwaco-2023-papers/5/Borro...
> Hylo is a language for high-level systems programming that promises safety without loss of efficiency. It is based on mutable value semantics, a discipline that emphasizes the independence of values to support local reasoning. The result—in contrast with approaches based on sophisticated aliasing restrictions—is an efficient, expressive language with a simple type system and no need for lifetime annotations.
> Safety guarantees in Hylo programs are verified by an abstract interpreter processing an intermediate representation, Hylo IR, that models lifetime properties with ghost instructions. Further, lifetime constraints are used to eliminate unnecessary memory allocations predictably.
https://www.hylo-lang.org/
https://github.com/Hylo-lang/Hylo
- Hylo a programming language that tries to be safe and fast
- Odin Programming Language
-
Why do lifetimes need to be leaky?
A model without lifetimes is also being explored in other languages, e.g. in Hylo. It sacrifices expressiveness, but on the other hand you don't have to deal with explicit lifetimes!
-
D Programming Language
Why go through all the trouble when you can do this: https://www.hylo-lang.org/ and not spend a second thinking of lifetimes? No, copies will not be issued unless necessary.
Or why not keep exploring this idea as well? More research-oriented than the first one right now, though, so take it with a grain of salt: https://vale.dev/
- Berry is a ultra-lightweight dynamically typed embedded scripting language
-
I've heard that "Rust's borrow checker is necessary to ensure memory safety without a GC" usually also implying it's the only way, but I've done the same without the borrow checker. Am I just clueless/confused?
Get rid of references at the cost of some expressivity (see Hylo, formerly Val)
- Rename 'Val' to 'Hylo'
What are some alternatives?
durexforth - Modern C64 Forth
carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
gforth - Gforth mirror on GitHub (original is on Savannah)
jakt - The Jakt Programming Language
lbForth - Self-hosting metacompiled Forth, bootstrapping from a few lines of C; targets Linux, Windows, ARM, RISC-V, 68000, PDP-11, asm.js.
vale - Verified Assembly Language for Everest
spf - SP-Forth
rust - Empowering everyone to build reliable and efficient software.
ucode - JavaScript-like language with optional templating
Vale - Compiler for the Vale programming language - http://vale.dev/
r4 - :r4 concatenative programming language with ideas from ColorForth.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.