BrokenC1oud/Core:master
master
Hello, I'm BrokenC1oud, and I'm interested in participating in GSoC 2026.
@@ -0,0 +4,4 @@
#[repr(C, packed)]
pub struct FileCommand {
pub func: u32, // 0 = read, 1 = read folder, 2 = create/write
Should be an emum
@@ -0,0 +7,4 @@
pub param1: u32, // offset (low)
pub param2: u32, // offset (high) or flags
pub param3: u32, // bytes to read/write
Why not just name them?
These parameters mean different things in different commands
Make different functions for different commands then
I don't get it, defining different structures makes it repetitive
I said functions, not structures. I definetely not allow structs with this names be in the repo
All file operations require the same struct quoting this for modification doesn't make sense
c023ca4534
d47ee35fa5
No dependencies set.
The note is not visible to the blocked user.
Hello, I'm BrokenC1oud, and I'm interested in participating in GSoC 2026.
WIP: file sys callsto add file sys calls@@ -0,0 +4,4 @@#[repr(C, packed)]pub struct FileCommand {pub func: u32, // 0 = read, 1 = read folder, 2 = create/writeShould be an emum
@@ -0,0 +7,4 @@pub func: u32, // 0 = read, 1 = read folder, 2 = create/writepub param1: u32, // offset (low)pub param2: u32, // offset (high) or flagspub param3: u32, // bytes to read/writeWhy not just name them?
These parameters mean different things in different commands
Make different functions for different commands then
I don't get it, defining different structures makes it repetitive
I said functions, not structures. I definetely not allow structs with this names be in the repo
All file operations require the same struct
quoting this for modification doesn't make sense
c023ca4534tod47ee35fa5View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.