It's cool to rewrite simple libraries to understand how code works at lower levels.
What style of formatting are you using? It seems peculiar at times.
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
It's cool to rewrite simple libraries to understand how code works at lower levels.
What style of formatting are you using? It seems peculiar at times.
Thanks for comment. I am using K&R style.
I'm not sure that's K&R style. In various places you have things where the thing that follows a for, while or if isn't indented, and as far as I'm aware, K&R indents religiously. K&R omits braces on single statements, sure, but that statement is nonetheless indented from the parent keyword.
e.g. you have things like:
while (condition)
statement;
and
for(x;y;z) {
if (condition) {
statement1;
statement2;
}
}
Which I'm pretty sure should be:
while (condition)
statement;
and
for(x;y;z) {
if (condition) {
statement1;
statement2;
}
}
respectively. The idea is that you can theoretically trace the keyword down to its closing brace, assuming there is one.
I didn't notice, it wasn't conscious. Thanks for the heads up. I fixed the indentation
Maybe add some context to the readme, what string.h does or is used for.
Thanks, I've just updated the README with a 'What is string.h?' section
Ohh, seems interesting. Not a C programmer, but still, thanks!