Adding to Kirk's post. I use a series of methods all prefaced with strt_IP (Start IP [vars])
each logical grouping (mostly system modules) has its own strt_IP method. these methods contain (hopefully) all IP var declarations, and assignments (for IP constants) used in that module. (maybe I need to do something similar for process vars...hmm....) All of these strt_IP methods are called during startup, ensuring that all IP vars are created and assigned values when running interpretedly. I also use all variables are typed, and have the compiler generate typing methods. For me - this has always caught all typing issues, including 1 vs 2 dimensioning of arrays. I have found that breaking up the IP vars in the manner descried above makes adding, updating, or changing a constants (permanent) value much easier. On Fri, 7 Oct 2016 16:29:46 +0000, Epperlein, Lutz (agendo) wrote: > Since we use this kind of arrays as constant arrays it could be > possible to put the declaration and the initialization in one place > and not in two different methods. And because we use the compiler > setting "all variables are typed", this place could be the Compiler_ > method. ********************************************************************** 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 **********************************************************************
