Re: What is wrong here? (Generic and controlled types)

[Robert Dewar <robert_dewar@my-deja.com>]

In article <8catei$n8$1@slb6.atl.mindspring.net>,
  swhalen@netcom.com wrote:
> Robert Dewar <robert_dewar@my-deja.com> wrote:
> : It is almost always possible to work around this trivially
by
> : simply including a controlled component in the type instead
> : of making the entire type controlled.
>
> : P.S. it is hard to see how the GNAT message could be any
> : clearer, suggestions welcome!
>
> 29.    package Real_Vectors is new Generic_Vectors(Real,
Index, Zero);
>        |
>     >>> instantiation error at generic_vectors.ads:23
>     >>> controlled type must be declared at the library level
>     >>>   (consider including controlled component instead
>     >>>    of making entire type controlled?)
>
> I know I'd appreciate getting a helpful hint like this, even
> though I have no reason to expect the compiler to do so.


For me that's going too far, since most often the solution is
simply to avoid the nesting that is causing the trouble, and
there are dozens of other possible solutions. TO fix on this
one would be misleading more often than not.

Yes, it would be nice if compilers could help write your
program for you, and they do try to help a bit, but if they
go too far in this direction, they start becoming actively
unhelpful. Finding just the right balance is not always easy.

Generally we avoid programming advice in messages unless it
is VERY likely to be correct, e.g. it is almost certainly
right to suggest adding ALL to make an access type general
when aliased is used incorrectly with a pool specific
access type


Sent via Deja.com http://www.deja.com/
Before you buy.