Re: Type safety, C++ and code generation
- From: "Jeffrey R. Carter" <spam.not.jrcarter@xxxxxxxxxxxxxxxx>
- Date: Fri, 28 Apr 2006 18:50:43 GMT
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"?
--
Jeff Carter
"Blessed is just about anyone with a vested interest in the status quo."
Monty Python's Life of Brian
73
.
- Follow-Ups:
- Re: Type safety, C++ and code generation
- From: Dmitry A. Kazakov
- Re: Type safety, C++ and code generation
- From: Randy Brukardt
- Re: Type safety, C++ and code generation
- 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
- Type safety, C++ and code generation
- Prev by Date: Re: gps vs gnat pro
- Next by Date: Re: Type safety, C++ and code generation
- Previous by thread: Re: Type safety, C++ and code generation
- Next by thread: Re: Type safety, C++ and code generation
- Index(es):
Relevant Pages
|