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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d927b7ea9b65580a,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-11-08 23:58:28 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!peer1.news.newnet.co.uk!news-peer.gradwell.net!not-for-mail
Newsgroups: comp.lang.ada
From: porton@ex-code.com (Victor Porton)
Date: Sat, 09 Nov 2002 11:39:32 +0500
Subject: Style: always declare subrountines?
Mime-Version: 1.0
X-Newsreader: knews 1.0b.1
Content-Type: text/plain; charset=us-ascii
Message-ID: <3dccc023$0$304$bed64819@news.gradwell.net>
NNTP-Posting-Date: 09 Nov 2002 07:58:28 GMT
NNTP-Posting-Host: 195.149.39.13
X-Trace: 1036828708 news.gradwell.net 304 mail2news/195.149.39.13
X-Complaints-To: news-abuse@gradwell.net
Xref: archiver1.google.com comp.lang.ada:30624
Date: 2002-11-09T07:58:28+00:00
List-Id: <comp.lang.ada>

How do you consider this:

If one would always declare every subrountine of a package body in the 
specification (in the public or in the private part) this excludes the
possibility that one may mistakedly create an internal subrountine with
the same specification as a not yet implemented public procedure and 
forget to implement this public procedure and so get wrong program
behavior.

Stylistic checkers for always declaring in package specification?