Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
Are there any pros and cons from performance standpoint? i.e,. does declaring all variables in global cause the task execution to take longer vs local declaration?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Global variables are using memory the entire time your program is running. Local variables will only use memory when a corresponding POU is running/being called. So theoretically, from a performance point of view, all your variables being global will slow down execution.
Most programmers and literature agree to minimise the use of global variables, largely because of how hard it is to debug and trace them. If you are using a global variable in multiple POUs, then to debug you have to follow the variable through each POU to find an issue. If you figure out a smart way to declare variables locally, then you can debug in just that POU, which is much easier.
I have written programs in my early days that used a lot of global variables. I even used some Goto statements in some C-Programming projects at uni. These solutions I used were flawed, because at the time, they seemed like an easy solution. But in the long run, they cause many issues in debugging and make the code a lot more complex than it needs to be.
I am aware of the debugging issues and possible complications with global variables. The only thing I was not sure about was the burden on the task cycle. Thanks again for your input.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are there any pros and cons from performance standpoint? i.e,. does declaring all variables in global cause the task execution to take longer vs local declaration?
Global variables are using memory the entire time your program is running. Local variables will only use memory when a corresponding POU is running/being called. So theoretically, from a performance point of view, all your variables being global will slow down execution.
Most programmers and literature agree to minimise the use of global variables, largely because of how hard it is to debug and trace them. If you are using a global variable in multiple POUs, then to debug you have to follow the variable through each POU to find an issue. If you figure out a smart way to declare variables locally, then you can debug in just that POU, which is much easier.
I have written programs in my early days that used a lot of global variables. I even used some Goto statements in some C-Programming projects at uni. These solutions I used were flawed, because at the time, they seemed like an easy solution. But in the long run, they cause many issues in debugging and make the code a lot more complex than it needs to be.
https://en.wikibooks.org/wiki/A-level_C ... _Variables m
Thanks PrinceACP.
I am aware of the debugging issues and possible complications with global variables. The only thing I was not sure about was the burden on the task cycle. Thanks again for your input.