Is R&K still the best way to learn C?

Is R&K still the best way to learn C?

Are the new things in C since the second edition worth learning/important?

Other urls found in this thread:

fabiensanglard.net/c/
twitter.com/NSFWRedditImage

C Primer Plus - Stephen Prata.

>R&K
>R&K.
>R & K
>R AND K

I did this. Do this.

Shit now I feel like a retard.

You are, but it's alright.

>R&K

I feel strange

C is a very small language. You can learn anything about it in less than a week, but you can learn anything about Scheme in an hour. You should start by "Structure and Interpretation of Computer Programs".

This.

Or C Programming: A Modern Approach by K.N. King if you are getting a little impatient as it's tad more brisk, but still comprehensive.

I use both.

>You can learn anything about it in less than a week
>very small language

It isn't a "very small language", it's relatively small. You're misunderstanding the difference. The C library can't be "learnt" in less then a week, there's still a bunch of functions to understand how to use safely. Then there's the rules of syntax in a multitude of areas.

It's RELATIVELY small, not "very small".

C is stupid easy. Being a code guru now, the only thing I haven't really gotten into much is meta programming and advanced optimization techniques, which you really don't need need unless you want to show off.

>Being a code guru now

But you're not.

More of a guru than most people.

That's like saying you are the smartest retard.

>More of a guru than most people

You're not a guru. You have a basic knowledge of certain areas of programming and you feel smarter than you are. Try to give advice without pretending that you're some kind of genius.

Society is ran on retards now, who would've thought

you can suck my pretentious dick.

I'll be willing to do that if it'll shut you the fuck up.

less talking more sucking, user.

So K&R or C Primer Plus?

K&R and Oreilly understanding c pointers
then a C data structures book
Then Advanced Progamming in the Unix Environment.

See ya in 18 months.

fucking shills I tell ya
>Guys I wanna learn C which book should I...
>Learn Scheme, read SICP!!

...

K&R only took me two days. Then, just practice and Google-fu.

>R&K
Were you dropped on your head as a child?

books recommended here: fabiensanglard.net/c/

The book by King-sama is gud too senpai

Get out the feminine penis then. Ante up, faggot.

I have to learn C++ for work purposes, is the best approach to learn C and then C++, or do I learn C++ straight-away?

This guy says it is

fabiensanglard.net/c/

I'm assuming you already know enough about programming and this isn't your first radio. Either way, I'd start with C++ though.

Imo C++ is still functional and useful in the future, while C is becoming more and more depreciated. I just personally feel it is better practice to learn C++, and if you find something in C++ that C does better ,than it's an easy thing to add in your project. Although I find those things are far and few in between.

Learn C because C is easier, smaller, and more useful. C++ is only useful for taking money from the wallet of fools (i.e. Windows programs)

How much do you know about encapsulation, inheritance and polymorphism?

well this. One of the best books up there.

learn modern C++ ffs

>the modernity meme that things made in 2016 are always better than things made in 2015

>modern
>C
>modern

As a non-programmer, I've found both and "Programming in C" by Kochan immensely better than K&R. K&R just throws meaningless terms at you without bothering to explain them in any meaningful way, it's not clear in its explainations etc. etc. As something to teach you, it's grossly overhyped and prime proof that someone who's good at designing something might not at all be adequate to teach others about the system.

That's probably just personal preference.
I like dense things, no matter what the topic, so K&R C was fun, enjoyable, and useful for me.

Learn c++ there really is not point in learning C first because everything you're gonna need from C is built right into c++. It's not necessary to learn C at all to learn C++ I would suggest thinking about them as two completely separate languages even though they are not.

>all of these people trying to get OP not to learn Unix's official programming language

Is it possible to write high end game engines like CryEngine or Unreal in C?

All languages compile to the same assembly which runs on the same physical hardware. Therefore, you can do anything with any language, provided the language doesn't explicitly prohibit you from doing something.

C explicitly prohibits you from having sex

But I had sex in February.

Best book coming through.

Programming in C has some mistakes, however. I noticed early on that he didn't distinguish the difference between a prefix and a postfix operator. He says that it's "just a matter of personal preference" and didn't mention the precedence of them at all or what they're used for.

At that point, I began to doubt the book. I'm only a beginner and even I know there's a difference between prefix and postfix.

That's why it says a modern "approach", you illiterate retard.

First time I've seen someone other than myself recommend it. Great book, highly recommend, OP.

99% of the time it doesn't make a difference at all.

But there's a difference, that's the point. The writer made no distinction and that could lead to bad habits forming. Thus, it's poor writing and poor guidance.

Bearing in mind the nature of algorithms, using a postfix increment instead of a prefix could fuck up the intended computation completely. Off-by-one errors galore.

Exactly this. C is a language without a lot of built in hooks for interacting with the OS. It relies heavily on libraries to provide those functions. C will teach you the logic, APITUE will teach you how to interact with your system.

so, is it outdated?

Should I just read K&R or should I be taking notes and running code examples, etc. ?

You should read the K&R
then you should be running some form of a UNIX system with access to man pages
I personally have all the man docs installed and a copy of the GNU libc manual for reference.
C it self is very simple, its when you interact with anything or want to do anything useful it gets complex

oh and btw alot of the examples can be hard to follow in the K&R book

I feel retarded I didn't answer your question
Programming is alot like math or any skill really in that you learn by doing.
You should be doing all the examples and rewriting them (NOT COPY+PASTING & RUNNING THEM)
and then also try to understand what the code is doing instead of blindly copying it.

then you should find a project you are interested in and try to understand the code base
and maybe even contribute to fix bugs that you think you can fix.

Contribute to a project that is already in motion? I've never heard of such a thing. Where do these things take place?

there are much more advanced and better written C books for beginners

this. it's unacceptable. just get a better book

I'll have to check some of these out. I mean, I have a basis on C/C++ but other than Shell scripts I really only use Python.

Which book is this from?

Pointers on C

what? explain yourself, computer-man.

>literally arguing like children on an image board in [current year] like it's [current year - 20]

You should definitely interact with K&R. After you learn what's in it, you can add to it.

what was Sup Forums like 20 years ago?

shit

>bothering to reply to the argument and even attach an image when it's allegedly below you

no, not unless you want to write C wrappers for those engines. in general, there's a reason they use c++: C is an absolute nightmare to do high-level graphics work with.

also kill yourself you fucking "i just wanna make games bruh" retard

>tells someone to kill themselves based on an assumption made based on one post

You're extremely unhinged. Seek help.

where do you think you are?