Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Classic programming books aka Kernighan and Ritchie
WTF. You aren't typical female. Looks like I threw my copy out when I was culling my library when I moved, together with tombs like Knuth. Didn't think I'd need them again, those things are all done for you now.
Maybe not typical (WTF does that mean anyway) but female nevertheless.
I couldn't part with that book.
+50 Xeno Geek Points Come back Toolpusher, scotspine, Voodooflux. Pogle
As for the rest of you - DILLIGAF
Purveyor of fine quality smut since 2005
CUK Olympic University Challenge Champions 2010/2012
My own contribution to the original requirement of the thread would be Leo Brodie's Thinking Forth - by succinctly describing and demonstrating how one should think so as to solve problems using Forth, it manages to describe and demonstrate how one should think so as to solve problems, full stop.
The section on Minimizing Control Structures is one that I still draw on today. I love finding a way to get control structures out of my code, which is probably one of the reasons I love XSLT, where one can almost always always eliminate control structures (which are close to meaningless in a declarative language anyway) by judicious use of predicates
I suppose I may as well address the pedants now: I know very well that the techniques one uses to eliminate control structures are just a way of driving the control structures down to a lower level: I am familiar with the way a computer that implements a von Neumann architecture works. The important thing is to get the control flow away from the code that actually says what's being done. Control structures are all about how, not what; but what is the meat.
The fact that one can also increase the potential parallelism of code by eliminating control structures is for another day
Anyone read any for other languages?
K&R's "C ...." was brilliant: concise, elegant, comprehensive primer
Computer books seem to be bloatware nowadays.
Kernighan & Pikes' "The Unix programming environment" was another very concise (if a little dry) tome.
Comment