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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f6ecb3f5b51ac219 X-Google-Attributes: gid103376,public From: bobduff@world.std.com (Robert A Duff) Subject: Re: Ada Readers (was Re: Coding Standards) Date: 1996/06/20 Message-ID: #1/1 X-Deja-AN: 161182393 references: <9606192024.AA12434@calstar3.lasc.lockheed.com> organization: The World Public Access UNIX, Brookline, MA newsgroups: comp.lang.ada Date: 1996-06-20T00:00:00+00:00 List-Id: In article <9606192024.AA12434@calstar3.lasc.lockheed.com>, wrote: >Robert A Duff wrote: >>What I don't understand is why we care so much about the READERS. Only >>the WRITERS can do damage. .... > >I hope I haven't missed anything significant in this thread, but my >perspective on "readers" of code is that of maintainers, and their >understanding of the intention and implemetation of the code is crucial to >their responsibility - keep the code real in all its future changing/expanding >missions. I think you're missing some context. I agree completely with what you say here. In the context of my comment above, maintainers are WRITERS -- that is, they can damage a program, because they modify it. Of course, they read it first, too. My point was just that if somebody is going to read some code BUT NOT MODIFY it, then I don't care so much whether that person truly understands it, and if they don't, nobody would notice. On the other hand, if the person is reading it in order to understand how to modify it, I care a *lot* whether they understand it properly. - Bob