Re: Prohibiting dynamic allocation for the given type

On 19 Mar, 04:06, gp...@[EMAIL PROTECTED]
 wrote:

> Ada is high level language

That does not matter.
Ada is a high level language, but still provides two ways to create an
object:

X : Type;
Y : Type_Ptr := new Type;

If these two methods are available, then apparently there is a
difference between them and this difference is not in *where* objects
are created, but *how long* they are allowed to live.

The high-level part of Ada can hide the "where" part, but not "how
long".

For some types I might want to prohibit one of these two ways of
object creation.

Prohibiting the first one is easy with limited types that have unknown
discriminants + factory functions that return pointers.

Prohibiting the second one seems to be impossible.
For me this is a limitation.

> What's wrong with good old comments atop of type declaration.

What's wrong with C with good comments? :-)

> But if you insist you may do run-time check by
> defining custom Storage_Pool pool for your object

Storage_Pool is a property of the pointer, not the type.

--
Maciej Sobczak * www.msobczak.com * www.inspirel.com