This is where strict variable nomenclature with typing info helps a lot. You can easily create a method that can gather all locals in a piece of code, and add the declarations at the top of a method. You can even apply that automatically using METHOD GET CODE and METHOD SET CODE. OTOH if you have no variable nomenclature with typing… 69000 typing errors. Forget it, seriously...
> Am 07.04.2017 um 18:29 schrieb Timothy Penner via 4D_Tech > <4d_tech@lists.4d.com>: > > Nigel, > >> I tried David Adams suggestion of trying ‘all vars are declared’ and at >> 69000 errors decided that was not the way to go! > > You really should try to fix those...That is 69,000 places that 4D is > guessing what the variable type should be - instead of you explicitly telling > 4D what the variable type should be. All you need to do is use C_TEXT or > C_LONGINT or C_* at the top of your methods to declare what the variables > are. This is the best practice after all. > > Just my 2 cents. > > -Tim > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
