Strucc.c - 2025-03-14

Dear All,
Dear CODESYS,

I'm curiously following CODESYS transitioning away from the CAA libraries, and I'm mostly in favor of these major changes. Naturally, I'd like to align my current (not end-user) developments accordingly.
I'm tracking , reading release notes, ... And want to figure out the future :)

Is it possible to hear / read more about the reasons, objectives and scope of these changes?

  1. One important element is CAA Types - CAA Types Extern. What is the plan with that?

  2. What's the future of CAA.SEMA, CAA.BOLT ?
    I have never used them (always relied on SysLib*), but they are tempting...
    Would be useful to have a platform independent "Macro" for this functionality...
    Is there something in existing or planned ?

  3. Are they suitable to be used in low level libraries...
    For Example IO-Drivers, Components, "to-become system libraries"?

  4. CAA.TaskLock, CAA.TaskUnlock ? Well, they don't claim platform independency, so I can't rely on those....

  5. Any up-to-date advise, standard, pattern to follow in new libraries for task and resource locking?
    Practical set of conditional defines to be used?

If this information is not publicly available, can you please send a private message about the proper way to achieve this? I have support agreement, just couldn't get trough with these questions...

P.

 

Last edit: Strucc.c 2025-03-14