OSDev.org

there were alot of warnings related to variable definitions after actual code had been compiled. Statements like: would error due to the 'x' variable being declared after a code statement such as 'i += 2;'. This also allowed me to clean up my code to make it look more organized and it assures me that there are no rogue variables laying around.

Also, with the c99 standard, prototypes needed to be placed to link functions in different files. I went through and made functions that didn't need to be used by other files 'static' as well as local variables. This actually cut down the size of my OS by 4-5k alone.

inflater wrote: Actually, you could start to sell your OS for money

I'm not sure of what you mean here?

Yayyak wrote:To me, following the language should be a no-brainer

true, but not many people actually use the strick warnings settings to enforce it though.

piranha wrote:I'm jealous, your OS actually has potential.

Thank you.

Also, thanks to Chase for adding a sweeeet feature I just noticed due to piranha's post. I didn't know that if someone posts on your thread while you are responding it notifies you. very cool.

01000101 wrote:I'm not sure of what you mean here?

I meant, that you could sell your OS. Like Windows/Mac OS.
Am I starting to write badly in English?

no, your english is fine.
I couldn't figure out if you were being sarcastic or not due to the context of the statement.

Thank you.

ps: a bit of a little insider info, DiNS is very close to supporting multiple processors/cores. I've written all the smp parsers + APIC startup routines, now I just need to finish the trampline code and set each core to a respected network card. The goal is to have each core dedicated to a network card.