Actually that is part of the problem -- misspelled variables, functions, etc. won't get caught until runtime. With language such as C, a lot of such problems do get caught during compile time -- and lint serves to catch other potential problems that won't get caught at compile-time. I find that misspellings are often hard to spot as the brain has a tendency to auto-correct for you. There are also occasions where I'd run into problems resulting from the auto-scoping of variables to PRIVATE resulted in a hard-to-debug situations.

>It's not as big a deal with VFP because all variables are dynamic. I'm not aware of a tool for VFP to do that.
>
>>Does anybody know of any software for VFP that performs a similar function as "lint" did for C code?
>>
>>In general looking for something that could warn me of possible problems such as undefined variable, function, procedure, property, method, table, field, etc. Sure, one could hand-check each module, but it is not only boring and tedious, but because of it it's likely you'll miss stuff..