Hey Tim, On Thu, Apr 27, 2017 at 10:43 AM, Timothy Penner via 4D_Tech < 4d_tech@lists.4d.com> wrote:
> So my understanding is, if you have written your own methods that begin > with compiler_ that are not specifically defined in the Database Settings > then use the Generate Typing button; then your custom method would be > treated as a regular method and 4D will add your declarations to the 5 > compiler_ methods that are defined in the Database Settings. Is that the > issue you are seeing? > Exactly. I can see why the compiler would want to say "if it's not on one of my compiler methods I don't know for certain it's right." But this leads to duplicating the declarations between the ones I make up and the others. Could it be an option to treat all methods that begin with "Compiler_" as equal? So if I have a method named Compiler_textVars with c_text(vText) in it the compiler won't duplicate that declaration in Compiler_variables. It's sort of like an extension of "all variables are typed" - if there's a problem I caused it. If it were a compiler option I'd still have the more conservative option of letting the compiler verify everything. I think it used to work that way a few versions ago but I may be wrong. To me it would make these sort of 'custom' declaration methods more useful. -- 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
