Re: Primitive curiosity...

["Jeffrey R. Carter" <spam.jrcarter.not@spam.acm.org>]

mockturtle wrote:
> 
> Is this actually implied by the RM description or is gcc
> being strict? (Maybe "immediately within" was given a
> technical sense, but I was not able to find the definition)
> 
> Why this?  There is some deep technical reason or is it
> just to enforce the programmer to be "order" and declare
> primitive subprograms close to the type definition?

This has to do with "freezing". When a type is frozen, all primitive operations 
of the type have been declared.

See ARM 3.9.2.13: "The explicit declaration of a primitive subprogram of a 
tagged type shall occur before the type is frozen (see 13.14). For example, new 
dispatching operations cannot be added after objects or values of the type 
exist, nor after deriving a record extension from it, nor after a body."

Deriving an extension from the type freezes it.

-- 
Jeff Carter
"Apart from the sanitation, the medicine, education, wine,
public order, irrigation, roads, the fresh water system,
and public health, what have the Romans ever done for us?"
Monty Python's Life of Brian
80