Books On Structured Design? 8
buzzword asks: "In the current climate of Object Oriented everything, it seems that no one is bothering to teach structured programming anymore. I dimly recall that there were several design methodologies and practices associated with non-OO programming which were powerful and not as arcane as the current method fascist stuff. Are there any books still in print that address this issue?"
Dahl, Dijkstra, and Hoare (Score:2)
Gerv
Re:Dahl, Dijkstra, and Hoare (Score:2)
I can't find a copy of this anywhere. Pointers?
Essence of program design (Score:2)
It's a slim book that concisely covers many ways of structuring your code (including OO):
Title: Essence of Program Design, 1/e
Author: Doug Bell, Sheffield Hallam University
Publisher: Prentice Hall
Copyright 1997, 200 pp.
ISBN 0-13-367806-7
I would give you a link to the publisher's page, but it doesn't have any more information.
Worth at least finding out if your library has it
Getting started - here's some pointers (Score:2)
Here's some ideas on how to get started.
Take a course in Data Structures, too. Of all the courses I took in college, this is one whose principles I still use each day. Knowing when to use scalars, vectors (arrays), linear or circular lists (singly- or doubly-linked), hashes, and databases... if the DATA is organized RIGHT, writing the algorithms to access it is GREATLY simplified! Use the right tools for the job.
I've seen too many programmers who just hack away at code until it seems to work -- great to see you trying to use other's knowledge and experience to bring some design and order into your programming! Good Luck!
Re:Getting started - here's some pointers (Score:1)
Sure... (Score:1)
Re:Dahl, Dijkstra, and Hoare (ISBN) (Score:1)
collections focus (Score:1)
This seems more for low-level stuff. It was interesting to learn (waaay back then), but I think that data modeling and generic collection interfaces (regardless of implementation since it might change) is a much more useful focus unless you will be doing something that is close to the equipment, such as embedded programming.
Many of the famous procedural texts are pre-relational, and that kind of bothers me.
I tend to see a wider role for tables than just persistence. Some non-SQL-based languages made tables much more pleasent than arrays. Arrays are the Goto of collections IMO.