3 ms·
Work your way through "A Book on C"? That's how I did it... Actually, I think the best approach would be to pick a project for which you can construct a belie
by dllthomas 12y ago
Work your way through "A Book on C"? That's how I did it...
Actually, I think the best approach would be to pick a project for which you can construct a believable (by you) reason why it should be in C. Some possible reasons:
1) You need precise control of hardware
2) You're running in an environment where higher level languages are not available
3) You need precise control of latencies
4) You need the absolute maximum possible performance
There are various projects with these requirements of various difficulties. I would say that it might be hard to simultaneously convince yourself that a project needs the maximum possible performance and also that it is tractable for you as a newbie C developer.
A simple kernel module might not be a bad thing, if you can do your development in a VM to recover from the inevitable crashes. The reason for C will be quite clear, but tooling will suffer.
Targeting microcontrollers will be similarly well motivated at a higher degree of awkwardness.