From: G. B. <nonlegitur@nmhp.invalid>
Subject: Re: how to force the Small aspect of a new type derived from the generic formal type ?
Date: Thu, 25 Jan 2018 18:35:36 -0000 (UTC)
Date: 2018-01-25T18:35:36+00:00 [thread overview]
Message-ID: <p4d81o$ds4$1@dont-email.me> (raw)
In-Reply-To: p4bj1f$s47$1@franka.jacob-sparre.dk
Randy Brukardt <randy@rrsoftware.com> wrote:
>
> ...; you can't use most representation
> aspects on a type derived from a generic formal type.
>
> Even if you were not in a generic unit, you can't usually put representation
> aspects on a derived type (they usually have to match the original type).
The “usually” calls attention to types derived from others
precisely to make their objects have a representation
that differs from those of the original type. (The case
when a type conversion changes the representation.)
Plausibly, this feature does not blend with types being generic
in any sense.
next prev parent reply other threads:[~2018-01-25 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 19:16 how to force the Small aspect of a new type derived from the generic formal type ? Mehdi Saada
2018-01-25 3:30 ` Randy Brukardt
2018-01-25 12:54 ` Mehdi Saada
2018-01-26 4:38 ` Randy Brukardt
2018-01-26 11:13 ` Alejandro R. Mosteo
2018-01-25 18:35 ` G. B. [this message]
2018-01-26 4:42 ` Randy Brukardt
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox