21–30 of 81 posts
Very good. A pet peeve is that it consistently says "sizeof()", like this: You can use the sizeof() operator to determine how many bytes of memory a certain type uses. (I know, sizeof() looks more like a function than an operator, but there we are.) BUT: sizeof does not in fact need the parentheses always! Syntactically they are part of the argument, and only needed when the argument is a type name, i.e. the argument…
Beej's Guide to Network programming ( http://beej.us/guide/bgnet/ ) is also pretty good. It was effectively used as the textbook in my networking class. (There was also an actual textbook, but almost nobody bothered to read it.)
Very good. A pet peeve is that it consistently says "sizeof()", like this: You can use the sizeof() operator to determine how many bytes of memory a certain type uses. (I know, sizeof() looks more like a function than an operator, but there we are.) BUT: sizeof does not in fact need the parentheses always! Syntactically they are part of the argument, and only needed when the argument is a type name, i.e. the argument…
About casting the malloc() : http://c-faq.com/malloc/mallocnocast.html
Beej's Guide to Network programming ( http://beej.us/guide/bgnet/ ) is also pretty good. It was effectively used as the textbook in my networking class. (There was also an actual textbook, but almost nobody bothered to read it.)
It's definitely worth reading, but be aware that it's quite old-fashioned in that it focuses entirely on blocking I/O and select(). Also this page fails to explain why you would call shutdown(): http://beej.us/guide/bgnet/output/html/multipage/shutdownman...
Beej's Guide to Network programming ( http://beej.us/guide/bgnet/ ) is also pretty good. It was effectively used as the textbook in my networking class. (There was also an actual textbook, but almost nobody bothered to read it.)
It's definitely worth reading, but be aware that it's quite old-fashioned in that it focuses entirely on blocking I/O and select(). Also this page fails to explain why you would call shutdown(): http://beej.us/guide/bgnet/output/html/multipage/shutdownman...
Earlier quoted context omitted.
It's definitely worth reading, but be aware that it's quite old-fashioned in that it focuses entirely on blocking I/O and select(). Also this page fails to explain why you would call shutdown(): http://beej.us/guide/bgnet/output/html/multipage/shutdownman...
What has replaced select()?
More reading: http://www.kegel.com/c10k.html
As someone who currently works with C# - is there much of a point to learning C? I've always found it interesting, but never had a reason to jump into it.
Nevertheless, I don't think anyone should call themselves a (true) programmer unless they know C.
C is easy to learn, because it's a small language. If you are not new to programming, pretty much all there is to know is in the second edition of the K&R book.
As someone who currently works with C# - is there much of a point to learning C? I've always found it interesting, but never had a reason to jump into it.
While C remains the single most important programming languages of all time, its share of popularity is shrinking, giving way to C++, C#, Java, and Swift (from Objective-C). Nevertheless, I don't think anyone should call themselves a (true) programmer unless they know C. C is easy to learn, because it's a small language. If you are not new to programming, pretty much all there is to know is in the second edition of t…
As someone who currently works with C# - is there much of a point to learning C? I've always found it interesting, but never had a reason to jump into it.
So, it depends on your objectives in programming. You don't need C or even C# if all you care is a job or an end objective (in fact, you would very much like to skip the programming part if possible). But if you care about programming as an activity of love, then the experience with C -- especially the one with few dependence of third-party libraries -- is uniquely rewarding.