Re: bindings with Ada 2012 aspects

["Randy Brukardt" <randy@rrsoftware.com>]

"Jerrid Kimball" <jerrid@kimball.co> wrote in message 
news:jn7egd$scs$1@munin.nbi.dk...
...
> As I see it, a pragma Export should be directly replaceable by interfacing 
> aspects' aspect marks and definitions:
>
> procedure Wait renames PO.Wait;
> pragma Export (C, Wait, "wait");
>
> becomes:
>
> procedure Wait renames PO.Wait
>    with Export => True, Convention => C, Link_Name => "wait";
>
> Am I looking at what should be submitted to ACT as a bug?

I believe this replacement is correct, except for one tiny detail:

No language-defined aspects are allowed on renames, and the above is a 
renames.

The reason is that almost all language-defined aspects are the same for all 
views of an entity, and a rename just introduces another view. Moreover, 
this renames "trick" exists for pragmas simply to get around the limitations 
of pragmas for overloaded entities, something that is totally unnecessary 
for aspects.

I think in this particular case, you are trying to create a wrapper with 
this renames (as opposed to "just" another view of the original subprogram). 
I think that allowing the original pragma is dubious (although an 
implementation is allowed to support Import and Export on anything they 
like -- but it certainly is *not* portable).

So, I think you need to replace this subprogram renames by a real subprogram 
(one that calls PO.Wait in it's body), and I suspect if you do that you'll 
have no problems with the aspects.

                             Randy Brukardt, Editor, ISO/IEC 8652:tdb. :-)