Re: procedure renames creates a primitive operation?

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

"Jere" <jhb.chat@gmail.com> wrote in message 
news:bc765307-02bd-4a38-b60c-4b743de6b3e4@googlegroups.com...
>I was curious if this was a bug or intended.
...
> I used a renames clause to bring a non primitive operation
> into scope (for client readability when calling the procedure).
> However, when I did that, it created a primitive operation.
> Is this correct behavior or a bug?

Yes, a renames of a non-primitive can be primitive. Similarly, a renames of 
a primitive can be non-primitive.

Its an intended bug. That is, it is generally acknowledged that this 
semantics is the worst possible choice (you've stumbled on one reason why). 
There are some really horrid consequences for things like class-wide 
preconditions. But it wasn't obvious what choice made sense at the time it 
was made in Ada 95. It's way too late to change now, of course.

                                  Randy.