From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.5-pre1 Path: eternal-september.org!reader02.eternal-september.org!aioe.org!yy9MKEJN2ULhWGfnfq4v5w.user.gioia.aioe.org.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Unreferenced parameters Date: Thu, 04 Feb 2021 10:48:51 +0000 Organization: Aioe.org NNTP Server Message-ID: References: <1361832d-7b30-4d55-b464-e046389f5380n@googlegroups.com> <23427583-e608-4134-ba8c-edfa106571ddn@googlegroups.com> NNTP-Posting-Host: yy9MKEJN2ULhWGfnfq4v5w.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: abuse@aioe.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (darwin) X-Notice: Filtered by postfilter v. 0.9.2 Cancel-Lock: sha1:vlhvrQOcwMwAbLw1xh7oc/gzzOA= Xref: reader02.eternal-september.org comp.lang.ada:61283 List-Id: "Dmitry A. Kazakov" writes: > I recently discovered yet another reason. When building an > encapsulated library, shoveling implementations inside the > specification breaks the library interface because implementation > packages must with-ed there. When with-ed from the bodies, as it > should be, the library interface includes only what it really must. This applies to any standalone library, I think. Now you've pointed it out, I'll certainly avoid using an expression function in a spec that requires me to 'with' (or 'private with') another package that I wasn't going to 'with' anyway.