This should be mandatory reading before you're allowed

File: 4thEnglish[1].jpg (50KB, 591x722px) Image search: [Google]

50KB, 591x722px

More like this

>>60069993
That is tougher than C unless you have read C before trying this.

>>60069993
C++ was a mistake

>>60069668
Solve Example 6.3 and post.
Copy paste and your mom dies.

File: 3529004414_8c59d52ed4_o[1].png (351KB, 755x977px) Image search: [Google]

351KB, 755x977px

Something like this

>>60070033
THIS

>>60070170
THIS

>>60070241
THIS

>>60070170
>>60070241
>>60070248
reddit

>>60071401
4chan

>>60071471
9gag

>>60071401
i wish mods would start autobanning anyone who mentions reddit in their post

>>60072242
THIS

>>60072256
THIS

>>60072448
THIS

File: sicp cover.jpg (51KB, 400x579px) Image search: [Google]

51KB, 400x579px

This

>>60069668
As a historical novelty, perhaps.

As a serious introduction to the C language, you must be out of your mind.

>>60070085
That's actually interesting.
Will try it out.

>>60073073
Name a better book.

>>60073312
Every broken tutorial your EE university shits out.

File: structured computer organization.jpg (126KB, 460x648px) Image search: [Google]

126KB, 460x648px

>>60069668
This too.

>>60070248
this

>>60073073
This is exactly what's wrong with C.

The book that describes how to program C in the way it was intended to be programmed in is a "historical novelty" and teaches "bad practices."

"Good C" that's sane, maintainable, and bug-free isn't C, it's C and fucktons of conventions, boilerplates, and other meta shit you're just expected to somehow know.

>>60069668
learning from literal books is pleb tier

>>60073457
Let me guess, you're "fluent" in LISP or Python?

File: Submissive White People.jpg (82KB, 488x437px) Image search: [Google]

82KB, 488x437px

>code monkeys think they're so superior that they should be the only ones allowed to post here

>>60073496
Not really.

I have a much better time reading a programming book than accessing a PDF document.

Hell, I'll put shit on my 50 buck kindle to read it instead of using my monitor, at least I can move the page around with my fingers(sort of).

>>60073766
It would be 100* better than the endless consumer electronics and /v/ tech support threads this board is plagued with.

>>60073755
Nah. Lisp is really cool, but impractical (with the exception of Clojure).

I'm an Erlang/Elixir guy. >:)

>there are people on this board RIGHT NOW who couldn't answer what the Fermi yields were
>there are people on this board RIGHT NOW who couldn't state what Fermi cards were made of
>there are people on this board RIGHT NOW who have no idea why Fermi was so deadly

fuck, why is it impossible to leave this increasingly shitty place?

>>60073807
Not really. The endless whining about Pajeet stealing your job and your gf gets old after a while too.

>>60073855
Those aren't actual programmers. Those are just idiots repeating memes for (You)s. I guarantee 99% of pajeetposters have never written a line of code in their life.

>>60073851
>wow i know about pointless shit

Please leave this board now. No one gives a shit about your old video cards.

>>60073922
Give him a break and be nice. Autistic people can't understand why other people don't care about what they care about in completely irrelevant contexts.

>>60073851
Let's say the average age on 4chan is 22. That would make the average 4channer 15 when Fermi came out. Given that most 15 year olds don't typically have the income to build PCs with $500 GTX 480s, it's not hard to see why most people here don't care about Fermi.

>>60069668
why?

Over the past week and a half, I have written around a 1000 lines of C89 to process a network protocol. This code that I have written is intended to eventually be running in the Windows kernel, and as such, I have designed it to not need to do any memory allocation or network communications on its own. Instead, it uses a single interface to read a TCP payload from some input buffer, and output a TCP payload to be written to some output buffer. Indeed, because of the way this program is structured, I am able to make this module only dependent on one C header -- stddef.h, and let some other module handle all of the memory allocation and network communication. As such, I can test the protocol processing code outside of the context of a kernel, and then drop it in later with no changes to the code.

I think it should be safe to conclude that I know how to write programs in C. Despite this, I have never actually read K&R C.

>>60073990
>I have written around a 1000 lines of C89 to process a network protocol.
literally, why?

>>60073922
>>60073949
>newfags
my point exactly

>>60074004

Security research involving decoy Windows drivers. Pretty much any KMDF stuff is required to be in C89, since Microsoft hasn't even fully implemented C99 in MSVC.

>>60073851

1.7, woodscrews, housefires? That shit was memed to death.