A warning would be enough. If after the INTO clause there are 2 or 3 variables, no problem, it will be very easy to detect the mistake. But sometimes that is not the case because there are 20+ variables and if variable 3 is called "lcName" and variable 24 is called "lcName" too, the programmer can have a hard time detecting the problem.
Greetings. Walter. On Thu, Feb 9, 2017 at 12:19 PM, 'Leyne, Sean' s...@broadviewsoftware.com [firebird-support] <firebird-support@yahoogroups.com> wrote: > > > Doug, > > > Delphi's latest compiler provides a hint in these cases: > > > > var > > x: Int32; > > begin > > try > > x := 0; > > x := 1; > > writeln(x); > > end. > > > > [dcc32 Hint] Project1.dpr(14): H2077 Value assigned to 'x' never used > > (Line 14 is the one assigning zero.) > > In hindsight my post should have read more like: > > - No compiler would treat the condition as an error. A warning, Yes. But > not an error. > > - There are plenty of DB tools (IBExpert for one) which perform their own > "syntax checking" and report warnings (though I would need to test if IBE > reports a warning for this case). > > - AFAIK, the FB engine only reports errors. So, a new set of > functions/methods would need to be developed to report and handle warnings. > > > Sean > > >
