You're right, this would be an absolutely useful feature. For me it's actually a show stopper to ever create any OOP code in Harbour. It's just too easy to mistype something and only get to know about it by live testing complete code flow.
Compiler-level solution doesn't seem to be easy though. Brgds, Viktor On 2010 Feb 22, at 14:01, Maurilio Longo wrote: > Viktor, > > yes. > > Maurilio. > > Viktor Szakáts wrote: >> Hi Maurilio, >> >> On 2010 Feb 22, at 09:02, Maurilio Longo wrote: >> >>> Viktor, >>> >>> one thing I'd like to have is the ability of the compiler to spot iVars like >>> it does variables, I mean unused, not declared and so on, while it now >>> simply >>> ignores all of them and you get an error when executing such code. >> >> By 'iVars', you means object vars? >> >> Brgds, >> Viktor >> >> _______________________________________________ >> Harbour mailing list (attachment size limit: 40KB) >> Harbour@harbour-project.org >> http://lists.harbour-project.org/mailman/listinfo/harbour >> > > -- > __________ > | | | |__| Maurilio Longo > |_|_|_|____| farmaconsult s.r.l. > > > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
