I prefer to run the compiler with the "all variables are typed" option. I also run the "Generate Typing" command before compiling. IN a lot fo projects I don't bother to separate out the typing commands from the ones 4D generates because it's just not important to me but that's another thread.
On the projects where I do create 'custom' Compiler_... methods to manage declaring things for certain modules or processes it's a real annoyance that 4D seems to ignore them in favor of logging what's in them again in the declaration methods it creates. Or is there an obscure setting I'm missing that let's me direct 4D in this regard? I thought I'd ask before putting up a feature request. It really detracts from the value of grouping the custom declarations together when 4D will go ahead and spread some other out where it chooses. And I like being able to run the command as part of a final sweep of things when compiling. And, yes, I am aware I can work around the limitations by adding a line the default docs 4D creates to identify new declarations it creates. -- 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 **********************************************************************
