Re: Multiple procedures in the same adb file?

[Robert A Duff <bobduff@shell01.TheWorld.com>]

"J-P. Rosen" <rosen@adalog.fr> writes:

> Le 12/01/2015 01:53, Robert A Duff a écrit :
>> This happened to me:  Existing code:
>> 
>>     function Some_Root_Package.Some_Function(...) return String;
>> 
>> Now I happen to know that it always returns String(1..20).
>> And returning known-length strings is more efficient,
>> and this one is a bottleneck, so it's worth changing to
>> something like:
>> 
>>     subtype String_20 is String(1..20);
>>     function Some_Function(...) return String_20;
>> 
>> But that doesn't work without adding a new package, which breaks
>> compatibility.  And this was a widely-used library, so I couldn't do
>> that.  And String_20 really doesn't belong in Some_Root_Package,
>> nor anywhere else than the package that Some_Function is (directly) in
>> (which didn't exist!).
>
> Put the function in a package, and declare Some_Function as:
> function Some_Function (...) renames New_Package.Some_Function;
>
> (For compatibility, new programs would use directly the function in the
> package).

I started to reply, "Good idea", but then I remembered it doesn't work.
A library unit can only rename another library unit.  If it did work,
I'd still prefer to use packages from the start.

I see AARM-10.1.1(14.a) explains why we have this restriction, in part
"because they wouldn't be particularly useful".  Probably written by
somebody who doesn't like library subprograms.  ;-)

- Bob