|
Paul, Thanks. I have a copy of "Who Knew.." While very good information on the "how to do it" side, it still doesn't touch the stuff Alan was talking about...functional deconstruction, abstraction, data hiding, encapsulation. It describes the tools one can use to do those things, but doesn't teach me the principles I can apply to break business problems into modular programming constructs. How to break out of a monolithic approach to thinking about logic flow, into an **ORGANIZED** modular approach, using small reusable pieces. I know, some people can study a tool, and intuitively know how they would want to use it. Perhaps these are the only people who should really be using the tool. I'm not like that. I think what I'm talking about is the distinction between the art and the science of programming. I don't know if the art can be learned, but I'd like to try. I'm hoping someone has written a book on it. Posts from Joe Pluta and Alan Campin and others indicate that one needs to study these high level programming/software engineering principles in order to do good programming. Maybe someone could suggest some specific authors/titles ? Greg --------------------------------------- Original Message: from: "Paul Morgan" <pmorgan@xxxxxxxxxxxxxx> subject: Re: Assembly programmers do it a byte at a time Greg, Download and read the 'Who knew you could do that with RPG IV' redbook at: http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg245402.h tml?Open. Paul
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.