https://forge.codesys.com/u/williamcorlin/2026-07-14T11:55:31ZRecent posts by williamcorlin2026-07-14T11:55:31Z2026-07-14T11:55:31Zwilliamcorlinhttps://forge.codesys.com/u/williamcorlin/https://forge.codesys.com3999ef2f57f74800b92b5047a0f77cbf585d6fc1

<div class="markdown_content"><p>I've been moving in the same direction. For new libraries, I'm trying to minimize dependencies on APIs that look like they're being phased out unless the documentation explicitly recommends them.</p> <p>For synchronization primitives like CAA.BOLT and CAA.SEMA, I'd love to see an official replacement or abstraction layer that's guaranteed to remain stable across runtimes. That would make library development much cleaner than relying on platform-specific SysLib* implementations or conditional compilation everywhere.</p> <p>Until there's clearer guidance, my approach has been to isolate the locking mechanism behind a small wrapper interface. If CODESYS changes the recommended API in the future, only that wrapper needs to be updated instead of every library that uses it. It isn't perfect, but it's made maintenance much easier.</p></div>