3 ms·
Not to mention it's the second edition from 1997. Hasn't anything happened in OOD/OOP during the last 15+ years that would make it worth updating? Edit: I ju
by smoyer 14y ago
Not to mention it's the second edition from 1997. Hasn't anything happened in OOD/OOP during the last 15+ years that would make it worth updating?
Edit: I just skimmed the table of contents (11 pages) and while I suspect there are some nuggets of gold in the book, I'm not sure they're worth reading 1500 pages. I've found that the problems new developers have with OOD/OOP are architectural and generally related to a specific language and/or framework.
- sixbrx 14y agoI think it would be worth perusing (not buying), just to see if he still recommends that procedures (routines with side effects) should never return any value, but should instead set one or more member variables - one or more per procedure - which callers should access after the call by separate getter methods. Really.