Ferdinando:

These are the standard for the method where the compiler will look to declare 
the variables the way you want them. If you do not do this, then the compiler 
will declare the variables as it comes across them. I do not remember which 
version this became the rule, but it has been for several versions.

In the Design menu, select the Database Settings menu item. In the Structure 
Settings dialog go to the Compiler page. Notice that all Compiler Methods are 
predetermined to be set as ‘Compiler_’ prefix, and you get to set the rest of 
the name.

We have used these for many years. I think it is important to use them even 
when coding and testing in uncompiled. At startup in uncompiled we will call 
the methods that declare interprocess variables. On the launch of a new process 
we always call the methods that declare process variables. This way your 
application is more likely to behave as expected.

Of course most of this ‘knowledge’ has come from courses I attended - and as 
usual I can be wrong.



Jody Bevan
Developer
Argus Productions Inc. <https://www.facebook.com/ArgusProductions/>
+1 587-487-6120



> On May 2, 2018, at 7:15 AM, stardata.info via 4D_Tech <[email protected]> 
> wrote:
> 
> Hi All,
> 
> I convert one application to V16.
> I notice that there are some new methods named compiler_...
> 
> I declare already all my variables, and now because 4D has created these new 
> methods?
> Are for to optimize the compiled code?
> 
> Thanks
> Ferdinando

**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************
  • Compiler_ Methods stardata.info via 4D_Tech
    • Re: Compiler_ Methods Jody Bevan via 4D_Tech

Reply via email to