[#532] Update C++ readmes with a more detailed memory layout requirem…

…ent description

examples/cxx/domains/README.md

@@ -31,6 +31,20 @@ not receive any data.
 
 ## Implementation
 
+> [!CAUTION]
+> Every payload you transmit with iceoryx2 must be compatible with shared
+> memory. Specifically, it must:
+>
+> * be self contained, no heap, no pointers to external sources
+> * have a uniform memory representation, ensuring that shared structs have the same data layout
+> * not use pointers to manage their internal structure
+>
+> Data types like `std::string` or `std::vector` will cause undefined behavior
+> and may result in segmentation faults. We provide alternative data types
+> that are compatible with shared memory. See the
+> [complex data type example](../complex_data_types) for guidance on how to
+> use them.
+
 To achieve this, we create a copy of the global configuration, modify the
 setting `config.global.prefix` using the user-provided CLI argument, and then
 set up the example accordingly.

examples/cxx/event_based_communication/README.md

@@ -2,6 +2,20 @@
 
 ## Running The Example
 
+> [!CAUTION]
+> Every payload you transmit with iceoryx2 must be compatible with shared
+> memory. Specifically, it must:
+>
+> * be self contained, no heap, no pointers to external sources
+> * have a uniform memory representation, ensuring that shared structs have the same data layout
+> * not use pointers to manage their internal structure
+>
+> Data types like `std::string` or `std::vector` will cause undefined behavior
+> and may result in segmentation faults. We provide alternative data types
+> that are compatible with shared memory. See the
+> [complex data type example](../complex_data_types) for guidance on how to
+> use them.
+
 This example demonstrates iceoryx2's event multiplexing mechanism in a more
 complex setup. The iceoryx2 `Publisher` and `Subscriber` are integrated into
 custom `ExamplePublisher` and `ExampleSubscriber` classes, which also

examples/cxx/publish_subscribe/README.md

@@ -10,7 +10,7 @@ instructions in the [C++ Examples Readme](../README.md).
 > memory. Specifically, it must:
 >
 > * be self contained, no heap, no pointers to external sources
-> * have a uniform memory representation -> `#[repr(C)]`
+> * have a uniform memory representation, ensuring that shared structs have the same data layout
 > * not use pointers to manage their internal structure
 >
 > Data types like `std::string` or `std::vector` will cause undefined behavior

examples/cxx/publish_subscribe_dynamic_data/README.md

@@ -12,7 +12,7 @@ allowing users to send samples of arbitrary sizes.
 > memory. Specifically, it must:
 >
 > * be self contained, no heap, no pointers to external sources
-> * have a uniform memory representation -> `#[repr(C)]`
+> * have a uniform memory representation, ensuring that shared structs have the same data layout
 > * not use pointers to manage their internal structure
 >
 > Data types like `std::string` or `std::vector` will cause undefined behavior

examples/cxx/publish_subscribe_with_user_header/README.md

@@ -10,7 +10,7 @@ instructions in the [C++ Examples Readme](../README.md).
 > memory. Specifically, it must:
 >
 > * be self contained, no heap, no pointers to external sources
-> * have a uniform memory representation -> `#[repr(C)]`
+> * have a uniform memory representation, ensuring that shared structs have the same data layout
 > * not use pointers to manage their internal structure
 >
 > Data types like `std::string` or `std::vector` will cause undefined behavior