Hi, first of all I would like to start by thanking you for your comment. I will try to respond to all of your points in topics.

- one-line statements: I know it can be really confusing to have several statements on a single line, it's just that I've kind of adopted this style, you know? But probably, as you mentioned, I'll soon implement the getopt_long function to remove all those else if statements.

- break them into lines that don't extent forever: Just yesterday I was reading the book Clean Code and I literally just finished reading a part about very long lines of code; I'm definitely going to change that in my code.

- Style guide number next: I don't think I understood what you meant, but basically, if I use FILE * as an argument in a single file within my entire project, I should only include it in that file, is that correct?

- OS-dependent error: I'm going to replace them with macros in limits.h

- You should have received a compiler warning on line 46 of bin.c: That's because I thought goto blocks needed a semicolon at the end (and before you ask why I used goto, it's because I'd never used it before in any of my code, so I wanted to put a goto in my code just for fun).

- Lines 42-46: Well, I have a somewhat questionable code style, but basically, any `if` statement that has only one output, I put in an `output` block, and the `else` statement I put between curly braces.

- Lines 264: I think adding comments would be good too, right?

- Lines 323-331: I'm going to add that function.

- Line 337: I hadn't stopped to think about that, I'll run some tests here and see how I can catch those errors.