Nigel, I went through a similar process several years ago when I changed the compile settings on a rather extensive database to 'all variables are typed.' I forget the number but it was a lot. Daunting.
I forget how much time I spent on it but it turned out to be much less than I thought it would and the overall improvement in the stability and quality of the project was substantial and I've never regretted it. As Tim suggested those are 69k instances where 4D is making a guess about what's going on. As you start specifying some loose ends they decrease dramatically. A single variable not typed could cause several dozen such errors which all go away as soon as it's corrected, for instance. So that number drops rapidly once you get going. Vincent's 4DPOP macro module (I think) includes a macro called 'Declarations' - you can run this inside of a method and it will find all the local vars, let you set the types and then write the declarations. On Fri, Apr 7, 2017 at 1:30 AM, Nigel Greenlee via 4D_Tech < [email protected]> wrote: > ... > and at 69000 errors decided that was not the way to go!..and could not > run his retokenise code because this is a live system i am working on and > its V12). Its feels better to me to have a system that does at least > syntactically correct and is compilable > -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 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:[email protected] **********************************************************************
