Hi Cannon, That is exactly what a constant is for. If the value is never changed, then those IP variables can easily be replaced by a constant.
Regards, Add On 11/1/16, 3:36 PM, "4D_Tech on behalf of Cannon Smith" <[email protected] on behalf of [email protected]> wrote: >The other solution would be to have 4D introduce the idea of a static >variable. So if I declared an interprocess variable the normal way, it >would not be allowed in preemptive processes. But if it was declared as >static, then it is only read only for any process once it is set so I >assume that a preemptive process could read this variable without issue. >This would solve most of my issues with interprocess variables in >preemptive processes. ********************************************************************** 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] **********************************************************************
