|
| "Gordon Sande" <g.sande@worldnet.att.net> wrote in message
news:2006052712085316807-gsande@worldnetattnet...
> The practical man is likly to say that the problem here is the
> GENERATION of the undefined values. That is when the execution should
> be flagged as erroneous. Letting them be and tracking them is
> awkward but seems to be an invented problem that is more the
> unintended result of the particular wording. Assign the problem
> to a thesis student and let the real world gt on with doing real
> things. If undefined variable checking were to be part of the
> standard then this is an issue that might deserve better wording
> but I would not expect it make any realistic checklist.
Checking undefined variables has been around for a long time
(more than 3 decades, maybe 4), and successfully in notable compilers
such as WATFOR/WATFIV and PL/C.
You will find that it's offered in some current Fortran compilers.
|
|