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.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!utgpu!watmath!clyde!att!ucbvax!AJPO.SEI.CMU.EDU!rracine From: rracine@AJPO.SEI.CMU.EDU Newsgroups: comp.lang.ada Subject: Limited Use Clause Message-ID: <8812061626.AA13093@ajpo.sei.cmu.edu> Date: 6 Dec 88 16:26:40 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet List-Id: Yet again the "use" clause is maligned. I did not get the author or the posting to include here, but the jist of the comment is that the 'use' clause should not be used (no reasons were given) and a more specific kind of 'use' clause should be available in Ada 9x. That is beginning to be the same as the statement "Ada tasking is too slow." People have said it so long (since it used to be true) that it is accepted without any arguments. Why not use the unrestricted 'use'? The only reason I have heard that can not be refuted is that it makes it hard to tell where to find things in source code. That argument is not a language issue, however. It is a Programming Support Environment issue. The compiler knows where the various procedures are declared. Why can't it give us a cross-reference listing at the end of each compilation? In the meantime, at least DEC has provided some tools that give some of this functionality, and I believe that there are some PC-based tools that allow one to find references to identifiers. Saying "Don't use 'use'" tells me a lot about a project. It is not using a sufficient APSE. It has people who complain about Ada, since they probably have difficulty reading their code. And they are probably behind schedule, for similar reasons. I hope this generates some discussion. Roger Racine C. S. Draper Laboratory, Inc.