BarinkOS/CoreLib/Memory.h

#pragma once

#include <stddef.h>
#include <stdint.h>

void* memset (void* ptr, int value, size_t num);

int memcmp( const void* ptr1, const void* ptr2, size_t num);

[[maybe_unused]] void memcpy (void* dest, const void* src, size_t count );

size_t strlen(const char* str);

int strncmp ( const char* str1, const char* str2, size_t num );

char* strtok(char* str, const char* delim , char**saveptr);
Moving certain aspects into their own static library Problem: As our kernel grows we need more complex datastructures and functions these would come from the standard C/C++ library with normal programs. The kernel is a freestanding programme and has no access to standard libraries. Solution: We build a mini version of the standard C/C++ library which will contain the datastructures and functions we want. This library can then be statically linked into our kernel binary. Making it a statically linked library also gives more structure to the project. Keeping these random functions and datastructures in the kernel just clutters the kernel source code with less relevant source code. 2023-02-19 22:38:32 +00:00			`#pragma once`

			`#include <stddef.h>`
			`#include <stdint.h>`

			`void* memset (void* ptr, int value, size_t num);`

			`int memcmp( const void* ptr1, const void* ptr2, size_t num);`

We can now open and read files on the harddisk through a messy virtual filesystem The uri has to contain 8.3 filenames for now as I have not yet figured out how to convert from that to regular filenaming for the name comparison. reading files is still limited to 1 sector 2023-02-26 12:44:41 +00:00			`[[maybe_unused]] void memcpy (void* dest, const void* src, size_t count );`
Fixup C++ compiler path in makefile of CoreLib memcpy implementation added 2023-02-25 19:04:34 +00:00
Moving certain aspects into their own static library Problem: As our kernel grows we need more complex datastructures and functions these would come from the standard C/C++ library with normal programs. The kernel is a freestanding programme and has no access to standard libraries. Solution: We build a mini version of the standard C/C++ library which will contain the datastructures and functions we want. This library can then be statically linked into our kernel binary. Making it a statically linked library also gives more structure to the project. Keeping these random functions and datastructures in the kernel just clutters the kernel source code with less relevant source code. 2023-02-19 22:38:32 +00:00			`size_t strlen(const char* str);`

Started fleshing out the storage API 2023-02-21 13:36:20 +00:00			`int strncmp ( const char* str1, const char* str2, size_t num );`

			`char* strtok(char* str, const char* delim , char**saveptr);`