From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_05,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,808505c9db7d5613 X-Google-Attributes: gid103376,public From: do_while@lo-pan.ridgecrest.ca.us (Do-While Jones) Subject: Re: Looking for good Ada95 book Date: 1996/11/19 Message-ID: <56shlp$4uf@ash.ridgecrest.ca.us>#1/1 X-Deja-AN: 197439421 references: <56b275$6k4@felix.seas.gwu.edu> organization: RidgeNet - SLIP/PPP Internet, Ridgecrest, CA. (619) 371-3501 newsgroups: comp.lang.ada Date: 1996-11-19T00:00:00+00:00 List-Id: Rich makes the valid point: > >2) And, reserved words do need to stand out in CS1. Much of the course >concerns learning the meanings of these words, which also act as roadmaps >to beginners for understanding code - because much of CS1 concerns algorithms >embodied in (nested) control structures. As students progress, abstractions >start to play a larger role, and the importance of reserved words diminishes, >and so can their prominence. > > That is certainly true from a student/instructor point of view. But I say, "Different strokes for different folks." As a maintainer of software, I would rather have the reserved words fade into obscurity. That is, I prefer procedure VIRUS is begin DESTROY_THE_DISK; end VIRUS; to PROCEDURE virus IS BEGIN destroy_the_disk; END; >From my point of view, reserved words are just noise that must be removed to obtain the information. When reserved words are emphasized I must expend more effort to ignore them. One of the wonderful things about Ada is that she doesn't put programmers in a style straitjacket. You can use whatever style emphasizes the things that are important to you. Do-While Jones -- +--------------------------------+ | Know Ada | | [Ada's Portrait] | | Will Travel | | wire do_while@ridgecrest.ca.us | +--------------------------------+