Re: Style: always declare subrountines?

[Jim Rogers <jimmaureenrogers@worldnet.att.net>]

Victor Porton wrote:

> [Posted and mailed]
> 
> In article <mailman.1036840502.30553.comp.lang.ada@ada.eu.org>,
> 	sk <noname@myob.com> writes:
> 
>>Hi, 
>>
>>
>>>... an internal subrountine with the same specification 
>>>as a not yet implemented public procedure ...
>>>
>>The "internal subroutine" IS the implementation of the 
>>"public procedure". 
>>
>>You will not be permitted, by the compiler to do the 
>>following ...
>>
> 
> You misunderstood. I'm about the case when one has forgotten
> to write the definition of the "public procedure", but
> written in the body a "private procedure" with the same
> specification.
> 

I personally do not think you should create style rules to try
to cover for bad design. Instead, you should improve your design
process. Your design process should make sure your package
specifications are correct before you build your package bodies.

Jim Rogers