kernel
hylo
kernel | hylo | |
---|---|---|
5 | 54 | |
731 | 1,128 | |
2.7% | 3.4% | |
8.6 | 9.9 | |
5 days ago | 3 days ago | |
C | Swift | |
GNU General Public License v3.0 only | 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.
kernel
-
Even the simplest possible assembly program will/can have a console window. How exactly?
You might find the source code for FreeDOS of interest for learning more about how the low-level access to the interrupt services worked. Specifically, console.asm installs a character write routine (which calls BIOS INT 10h under the hood).
-
Trying to run FreeDOS off CF Card on 286 homebrew system --- Question about bootloader and drive geometry information
Looking at https://github.com/FDOS/kernel/blob/master/boot/boot.asm, I see %define statements for this type of information, but I'm not sure how these memory locations are normally populated with proper values. Is this something that Sys does when preparing the CF card? Or should the BIOS populate this information when loading the boot loader?
-
"My Reaction to Dr. Stroustrup’s Recent Memory Safety Comments"
That's where I'm coming from. FreeDOS still gets occasional commits once per few months but is not really developed anymore. Watcom C still seems like it's actively developed, but it's not clear what they are trying to achieve if they are not even interested in what's happening in C/C++ world!
-
How to Port to ARM (Just Curious, not ready to do it yet)
Here's the code for the kernel https://github.com/FDOS/kernel/ You will have to entirely rewrite the Assembly code since it is x86 assembly (Netwide Assembler is great, but not for ARM). Namely boot code is assembly. The kernel does compile under multiple compilers. I'm not too sure if ARM platforms handle this, but I would look at the Linux kernel for boot code on ARM.
-
Are DOS utilities open source.
"DOS" is a little bit of a general term. Microsoft's product, MS-DOS, is not Free Software. But there are other implementations, including FreeDOS, which is compatible with MS-DOS.
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?
fdpp - FreeDOS plus-plus, 64bit DOS
carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
surface-aggregator-module - Linux ACPI and Platform Drivers for Surface Devices using the Surface Aggregator Module over Surface Serial Hub (Surface Book 2, Surface Pro 2017, Surface Laptop, and Newer)
jakt - The Jakt Programming Language
cacule-cpu-scheduler - The CacULE CPU scheduler is based on interactivity score mechanism. The interactivity score is inspired by the ULE scheduler (FreeBSD scheduler).
rust - Empowering everyone to build reliable and efficient software.
vale - Verified Assembly Language for Everest
static-assertions - Ensure correct assumptions about constants, types, and more in Rust
Vale - Compiler for the Vale programming language - http://vale.dev/
util-linux
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.