Re: API design problem - buffer scatter I/O
- From: "Dmitry A. Kazakov" <mailbox@xxxxxxxxxxxxxxxxx>
- Date: Tue, 25 Nov 2008 09:34:16 +0100
On Mon, 24 Nov 2008 21:59:41 -0800 (PST), christoph.grein@xxxxxxxxxxxxxx
wrote:
Sure it is. How a compiler represents data types (including access
types) is an implementation detail.
What I meant is the incompatibility between pointers to constrained
and unconstrained:
I agree with you. Pointer to a subtype is not necessarily a subtype of the
pointer to the base. That is not an implementation detail. It should be per
programmer's choice. Unfortunately Ada lacks means to propagate type
constraints between related types, which is the issue here. We need a way
to say whether the constraint has to be moved from the target to the
pointer, making the later unconstrained. That does not necessary imply that
the pointer's representation must become "fat." That indeed would be an
implementation detail, as Robert says. But the decision is not a detail.
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
.
- References:
- API design problem - buffer scatter I/O
- From: Maciej Sobczak
- Re: API design problem - buffer scatter I/O
- From: Robert A Duff
- Re: API design problem - buffer scatter I/O
- From: christoph . grein
- Re: API design problem - buffer scatter I/O
- From: Robert A Duff
- Re: API design problem - buffer scatter I/O
- From: christoph . grein
- API design problem - buffer scatter I/O
- Prev by Date: Re: Compiler quality (was: Extending discriminant types)
- Next by Date: Re: Compiler quality (was: Extending discriminant types)
- Previous by thread: Re: API design problem - buffer scatter I/O
- Next by thread: Re: API design problem - buffer scatter I/O
- Index(es):
Relevant Pages
|