<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: NCMV</title>
    <description>The latest articles on DEV Community by NCMV (@nguyenchiemminhvu).</description>
    <link>https://dev.to/nguyenchiemminhvu</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4111379%2F5771ee13-f4fb-46f5-bd1e-06a0044b1be0.jpg</url>
      <title>DEV Community: NCMV</title>
      <link>https://dev.to/nguyenchiemminhvu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nguyenchiemminhvu"/>
    <language>en</language>
    <item>
      <title>CASTLE – A modern C++ template library for safety-critical embedded systems</title>
      <dc:creator>NCMV</dc:creator>
      <pubDate>Sat, 05 Sep 2026 16:52:47 +0000</pubDate>
      <link>https://dev.to/nguyenchiemminhvu/castle-a-modern-c-template-library-for-safety-critical-embedded-systems-5hjk</link>
      <guid>https://dev.to/nguyenchiemminhvu/castle-a-modern-c-template-library-for-safety-critical-embedded-systems-5hjk</guid>
      <description>&lt;p&gt;&lt;a href="https://github.com/nguyenchiemminhvu/castle" rel="noopener noreferrer"&gt;https://github.com/nguyenchiemminhvu/castle&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’ve been working on &lt;strong&gt;CASTLE&lt;/strong&gt; — Common Automotive Safety-critical Template Library for Embedded engineers.&lt;/p&gt;

&lt;p&gt;The name is intentional: the library was originally motivated by a simple goal — building small, predictable C++ building blocks for automotive and other safety-critical embedded systems.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;CASTLE&lt;/strong&gt; is a prototype C++17, header-only library built around a few embedded-friendly constraints:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;no heap allocation&lt;/li&gt;
&lt;li&gt;no exceptions or RTTI&lt;/li&gt;
&lt;li&gt;fixed-capacity, statically bounded data structures&lt;/li&gt;
&lt;li&gt;predictable resource usage&lt;/li&gt;
&lt;li&gt;compile-time configuration where practical&lt;/li&gt;
&lt;li&gt;lightweight, composable components&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It currently includes fixed-capacity buffers, callbacks, event and signal dispatching, timers, logging, iterators, bit utilities, safe numeric casts, and other small utilities.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;CASTLE&lt;/strong&gt; was inspired by the &lt;a href="https://github.com/etlcpp/etl" rel="noopener noreferrer"&gt;Embedded Template Library (ETL)&lt;/a&gt;, but takes a somewhat different approach, focusing on a more modern C++ coding style and more expressive APIs. In particular, I’m exploring more convenient ways to build event-driven embedded software while keeping memory usage bounded and behaviour predictable.&lt;/p&gt;

&lt;p&gt;This is still a prototype, so I’m sharing it mainly to get feedback from people working with embedded C++, automotive software, or safety-critical systems.&lt;/p&gt;

&lt;p&gt;Planned additions include fixed-capacity containers, finite state machines, protocol I/O, encoders/decoders, CRC and checksum algorithms, and more compile-time configuration for event-driven systems...&lt;/p&gt;

&lt;p&gt;I’d particularly like to hear where you think this approach makes sense, where it doesn’t, and what would make CASTLE more useful in a real embedded project.&lt;/p&gt;

</description>
      <category>cpp</category>
      <category>automotive</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
