Re: Type safety, C++ and code generation
- From: "Dmitry A. Kazakov" <mailbox@xxxxxxxxxxxxxxxxx>
- Date: Fri, 28 Apr 2006 21:55:48 +0200
On Fri, 28 Apr 2006 18:50:43 GMT, Jeffrey R. Carter wrote:
brian.b.mcguinness@xxxxxxxx wrote:
One solution to the problem would be to provide a new keyword for
defining types with no default operations. Only the operations you
explicitly defined would be available.
You mean like "limited private"?
I don't think that would be a good idea.
Ada.Finalization.Limited_Controlled is a better way. The language offers an
abstract base type to derive from. No keywords needed.
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
.
- References:
- Type safety, C++ and code generation
- From: Maciej Sobczak
- Re: Type safety, C++ and code generation
- From: REH
- Re: Type safety, C++ and code generation
- From: Maciej Sobczak
- Re: Type safety, C++ and code generation
- From: REH
- Re: Type safety, C++ and code generation
- From: Maciej Sobczak
- Re: Type safety, C++ and code generation
- From: Georg Bauhaus
- Re: Type safety, C++ and code generation
- From: Maciej Sobczak
- Re: Type safety, C++ and code generation
- From: Georg Bauhaus
- Re: Type safety, C++ and code generation
- From: brian . b . mcguinness
- Re: Type safety, C++ and code generation
- From: Jeffrey R. Carter
- Type safety, C++ and code generation
- Prev by Date: Re: Type safety, C++ and code generation
- Next by Date: Re: where exactly c++,c fail and Ada gets thru'
- Previous by thread: Re: Type safety, C++ and code generation
- Next by thread: Re: Type safety, C++ and code generation
- Index(es):