spec/body/rep (Was: Compilation error (GNAT bug?))

[Georg Bauhaus <rm-host.bauhaus@maps.futureapps.de>]

On 20/05/14 20:43, Simon Wright wrote:
> Victor Porton <porton@narod.ru> writes:
>
>> package My is
>>
>>     procedure C_Raptor_New_World
>>       with Import => True, Convention => C, External_Name => "raptor_new_world";
>>
>> end My;
>>
>> $ gnat compile -gnat2012 my.ads
>> gcc-4.6 -c -gnat2012 my.ads
>> my.ads:4:11: aspect identifier expected
>> gnatmake: "my.ads" compilation error
>>
>> Why it does not compile? Is it a GNAT bug?
>
> No, just an old version of GNAT. GCC 4.7 fails too; 4.8 is OK. GNAT GPL
> 2011 fails; 2012 is OK.

  procedure Foo (Arg : in out T)
    with
       Global => ...
       Pre => ...
      Post => ...
      Convention => ...
      External_Name => ...
      Linker_Options => ...
      Inline;

Some aspects, such as Linker_Options, are about things outside the
program. A Convention identifier less so, it addresses any client of
package My and insofar belongs in the public part with the declaration.
Then there are aspects of still other kinds, such as Pre/Post conditions
of contracts. They cannot very well exist without their declarative item,
just like pragmatic aspect Inline, although the latter may written
separately.

The pin board style list of aspects just lumps all of these different
kinds together after "with".

What if the "external aspects" went elsewhere? For example, in a
representation unit. (That's a name I remember). With rep units,
the source text proper becomes more portable, and more configurable
at the same time. There is no need to change aspects in the source
text when switching environments or when changing the configuration
(Linker_Options is one example). Just pick a suitable rep unit.
Declarations also become more readable, insofar as they'd focus on
just the logic, not link names and such.

Representation units can provide an Ada version of dependency
injection, even when injection happens at compile time.

In fact, GNAT already supports "outsourcing" certain aspects with the
help of project files. Do some of the other compilers do that, too?

Since aspects are a fairly new addition to the language, chances
are that representation units will not generate backwards compatibility
issues.

Would representation units help producing clear separation of concerns?