Code which every programmer must read before dying
21–30 of 38 posts
Re: Code which every programmer must read before dying
#22Re: Code which every programmer must read before dying
#23Literate programming is the style of programming that's intended to be read: http://www.literateprogramming.com/ Quite the contrast with the Bourne Shell: "Nobody really knows what the Bourne shell's grammar is. Even examination of the source code is little help." – Tom Duff http://en.wikipedia.org/wiki/Bourne_shell#Quotes
[edit] michaelcampbell has already recommended it below - missed that.
Re: Code which every programmer must read before dying
#24Re: Code which every programmer must read before dying
#25I think a very good example of when OOP is genuinely useful and desirable is the Twisted Networking Engine: http://twistedmatrix.com/trac/browser/trunk/twisted
Re: Code which every programmer must read before dying
#26Earlier quoted context omitted.
Crikey, that's like recommending the Bourne Shell (which was a bunch of macros so you could write ALGOL-like code in C)! http://en.wikipedia.org/wiki/Bourne_shell#Quotes twisted is, well, twisted. And that's what it does to your head too.
Just to clarify, I'm not talking about event-driven programming, errbacks and callbacks, but rather how they've done all of the abstraction of the different protocols and subsystems. It's one of the few times where I've considered inheritance absolutely essential.
Pretty much every other reactor system is cleaner and easier.
I fight twisted every day and rue the day I picked it for a big project.