Re: Dynamic Variant Record Creation

[Robert A Duff <bobduff@shell01.TheWorld.com>]

Warren <ve3wwg@gmail.com> writes:

> *.adb:327:13: warning: variable "Result" is read but never assigned
>
> Perhaps a dummy assignment after I am through with it
> would be enough. Is there a better way of dealing with
> the warning? 

When a warning is a false alarm, I think the appropriate way to
deal with it is to use pragma Warnings.  There's a rich variety
of features to suppress warnings on a fine-grained or coarse-grained
basis.  See the docs.

But first make sure you really believe it is a false alarm,
and then put in a comment explaining why.  (Sounds like
in this case, it's OK because you have no components
besides the discriminant).

Contorting the code (e.g. inserting a dummy assignment) is
rarely the way to go.  Neither is it a good idea to simply
ignore them -- you should be able to have a clean (warning-free)
build.

In fact, I'd go so far as to say a compiler that gives
warnings (some of which are false alarms) is broken
if it doesn't support some way to suppress them.

Warning: pragma Warnings is GNAT specific.  But that's OK;
it won't harm portability.

- Bob