cyt "Why declaring local variables as static ?

/Bruno "


Because it was in the documentation.

Object Reference Manual
-pwrb
-Plc
-DpDistribute

Ok!

Claes did it, so it's the way to do it and it means the object has to be remain from scan to scan

(I have not yet use Dpcollect, I prefer CArithm)

/Bruno

Hi Bruno,

Actually it doesn't have to remain to the next scan, but it has to remain until the DpDistribute is executed. The code in the DataArithm is surrounded by curly brackets, so declared variables will be freed at the end of the DataArithm code. If they are placed on outputs to be read by other objects they have to be declared static to still be valid when these objects are executed.

/Claes

Hello Claes,

Thank's very much, I think I got now the big picture.

/Bruno