> Start with ADD in Chapter 7, where 15 instructions are concisely compressed > into a meaningless hotchpotch of description.
That is an excellent point. The description would get a lot clearer if it just detailed one instruction. That could be a significant improvement. I'm sure IBM can come up with a mechanism to create such an end result without replicating every spec of information in the description of every instruction it applies to. That would make life easier for the authors and prevent errors in new versions. I don't think I care much about the grouping of the instructions. Like others said: I mostly start in the index. I do think there is some sense in grouping instructions that require privileges to execute in a different chapter. I only write application level software and wouldn't want the control instructions mixed with the 'regular' instructions. Fred! ----------------------------------------------------------------- ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. -----------------------------------------------------------------
