xC Task scope variable initial value

[teachop]

The variables in a task look like automatics in a c function. In c the initial state for automatics is unknown. Is this also true of task scope variables in xC, or are they guaranteed to be zero like file scope or global variable would be in c?

Thanks!

[davelacey]

They have an undefined initial value. There are no "tasks" as such in the language. You just have functions like in C. We tend to call them tasks if their main use case is to be called to run in parallel via a 'par' statement.

[teachop]

Thank you! Also your description of tasks is helpful, I had assumed that par{} triggered special code generation for the function. I have lots to learn...