How about check_locals? You can check for both unused and potentially unassigned locals.
> On Mar 7, 2014, at 5:39 PM, Leah Hanson <[email protected]> wrote: > > Adding that to TypeCheck sounds pretty reasonable. Functions already provide > their local variable names, so it would be a matter of finding all variable > usages (excluding LHS assignments). I can probably find time in the next week > or so to add it. Maybe "check_for_unused_local_variables"? (which seems long, > but descriptive) > > -- Leah > > >> On Fri, Mar 7, 2014 at 4:02 PM, Jiahao Chen <[email protected]> wrote: >> On Fri, Mar 7, 2014 at 4:22 PM, Stefan Karpinski <[email protected]> >> wrote: >> > I would prefer to have opt-in (but easy to use) code analysis that can tell >> > you that "anwser" is an unused variable (or in slight variations of this >> > code, that "answer" or "anwser" is always or sometimes not assigned). >> >> That sounds like -Wimplicit in fortran compilers, which forces IMPLICIT NONE. >
