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.9 required=5.0 tests=BAYES_00,LOTS_OF_MONEY autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,2a687662f09731bb X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!news4.google.com!news.glorb.com!cycny01.gnilink.net!spamkiller.gnilink.net!gnilink.net!trnddc06.POSTED!20ae255c!not-for-mail Newsgroups: comp.lang.ada From: Anonymous Coward Subject: Re: Don't use the "use" clause References: <1132227919.9036.51.camel@sonnenregen> <1132233886.11218.11.camel@sonnenregen> User-Agent: slrn/0.9.7.4 (Linux) Message-ID: Date: Thu, 09 Feb 2006 05:13:04 GMT NNTP-Posting-Host: 141.149.87.138 X-Complaints-To: abuse@verizon.net X-Trace: trnddc06 1139461984 141.149.87.138 (Thu, 09 Feb 2006 00:13:04 EST) NNTP-Posting-Date: Thu, 09 Feb 2006 00:13:04 EST Xref: g2news1.google.com comp.lang.ada:2817 Date: 2006-02-09T05:13:04+00:00 List-Id: In article , wrote: > > Someone, I forget who, once said that "People who make up strict > rules for programmers tend to be people who no longer write > production programs - or never did." While this probably does not > apply to you, it does seem to fit a lot of people who invent coding > standards. I find that the strictest of coding standards is a great benefit to the largest and least disciplined developement teams. Excessive use of the use clause (along with other sloppy programming practices like excessive global variables) calls for restraints. Your typical variety of C programmers who learned the Ada syntax on the job and are drawn to a Windows environment is the stereotype that comes to mind. The shortcoming of strict rules is negligable compared to mess that it prevents in this situation. OTOH, disciplined, experienced Ada developers who don't abuse the unruly and lenient constructs (use clause, gotos) can be more productive without the restrictions. The latter is a rare case. I'm currently working in an environment that has no restrictions, and most of the staff is quite disciplined and knowledgable. However there are a couple exceptions. I have been forced to write subprograms to export private types of some of my packages as a public types, because the user of my package (who is new to Ada) just wants a plain float, or an integer.