Skip to content
This repository

Open source operating system using the metodo kernel

tag: v0.0.1

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 boot
Octocat-spinner-32 docs
Octocat-spinner-32 drivers
Octocat-spinner-32 hal
Octocat-spinner-32 include
Octocat-spinner-32 init
Octocat-spinner-32 kernel
Octocat-spinner-32 lib
Octocat-spinner-32 mm
Octocat-spinner-32 tools
Octocat-spinner-32 userland
Octocat-spinner-32 .gitignore
Octocat-spinner-32 DIRS
Octocat-spinner-32 LICENSE
Octocat-spinner-32 Makefile
Octocat-spinner-32 README
Octocat-spinner-32 debug.sh
Octocat-spinner-32 link.ld
README
You MUST use comments in your code.
 
Use K&R C. Always.
See what Wikipedia has to say: The K&R style, so-called because it was used in Kernighan and Ritchie's book The C Programming Language, is commonly used in C. It is less common for Objective C, C++, C#, and others. It keeps the first opening brace on the same line as the control statement, indents the statements within the braces, and puts the closing brace on the same indentation level as the control statement (on a line of its own). Functions, however, are braced distinctly from statements; an opening function brace is placed on the line following the declaration, at the same indentation level as the declaration. This is because in the original C language, argument types needed to be declared on the subsequent line, whereas when no arguments were necessary, the opening brace would not appear in the same line with the function declaration.
int main(int argc, char *argv[])
{
    ...
    while (x == y) {
        something();
        somethingelse();
        if (some_error)
            do_correct();
        else
            continue_as_usual();
    }
    finalthing();
    ...
}
 
Simplicity is beautiful.
 
Use Intel ASM. Always.
 
 
Something went wrong with that request. Please try again.