Re: argument of conversion cannot be an allocator

[dewar@merv.cs.nyu.edu (Robert Dewar)]

Dale asks

<<Ah, so are you saying the the type conversion (a_ptr) only "looks at"
the "new", and can't deduce (or doesn't have to) the resultant type from
the "new b"?>>

Not quite, obviously you cannot tell the type of "new x
" by looking at it in isolation (it could be any of a number of different
access types). So you can only use "new x" in contexts where you can figure
out the required type using normal overloading rules, in a way that gives
a unique answer.

But in a type conversion, you only know what type you are going TO, not
what you are coming from, so the type you are coming from must be
uniquely determined by the expression being converted.

I often find that people get type conversions and type qualiffication
badly mixed up, and use the former when they want the latter. I think
that is what happened to you in this case. 

For example, suppose we have two functions

   function f return integer;
   function f return real;

then

    integer(f)

is clearly illegal, since it is ambiguous, but
integer'(f) is fine, and is the proper way of making sure you
get the version of f you want.

type conversions of pointers are unusual
type qualifications of allocators are often required