Well, I have been developing my own implementation of the C Standard for UNIX platforms (only tested on Linux, though). It's going very well and I'm very glad that I managed to implement the whole stdio library except for 'printf and its friends (sprintf, scanf...)', since this will be a really tough work. In fact, I was looking to find an already available Open-source implementation.
I must say that the hard part was starting with the FILE structure and, eventually, having to steadily modify it to fit the needs of each function, such as ungetc and etcetera. Implementing a wrapper to kernel calls was also tough, but - hey - I'm alive.
What I've come to understand with this "hobby of mine" is that, while following the standard might be portable, it seems to hit performance, since it seems to me that the standard implementations are merely wrappers (with additional features which slow it down) to the 'real' functions.
So if we know that we will be targeting a given platform and that our code doesn't have to compile on another, does it seem reliable to directly use an Operating System's API and System Calls? Sure it'll break portability, but it will increase performance.
And I think that this all happens because the maintainers of the operating systems do not implement themselves the standard. AFAIK it was born in UNIX and everything should support it natively! But that's just silly me who is angry at some companies.
Also, given that I wanted to have printf and its friends working, can someone point me to an available implementation? I'd look for every implementation-specific functions such as writing/reading operations, file structure manipulation and others and replace them with my own functions.
Thanks, sorry to bug you,