From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: null exclusion and generics
Date: Thu, 19 Oct 2006 15:06:35 +0200
Date: 2006-10-19T15:06:35+02:00 [thread overview]
Message-ID: <1fzlvq64mofpu.hh36uqejgir2.dlg@40tude.net> (raw)
In-Reply-To: 1161262319.24061.19.camel@localhost.localdomain
On Thu, 19 Oct 2006 14:51:59 +0200, Georg Bauhaus wrote:
> If a generic formal type is private, I can supply a
> null excluding subtype for the type parameter.
> A generic formal private type means assignment is possible.
> Declarations of objects of the null excluding
> actual inside the generic need explicit initialization,
> though.
>
> generic
> type T is private;
> procedure Nop(source: in T);
Is it really so? I would expect them to require:
generic
type T (<>) is private;
procedure Nop(source: in T);
for "not null" is a constraint.
What would a language layer say?
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
next prev parent reply other threads:[~2006-10-19 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 12:51 null exclusion and generics Georg Bauhaus
2006-10-19 13:06 ` Dmitry A. Kazakov [this message]
2006-10-19 20:08 ` Randy Brukardt
2006-10-20 7:57 ` Dmitry A. Kazakov
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox