@Blitz motorsToday’s spotlight: Exploring best practices in embedded systems, with a focus on operating systemsToday’s spotlight: Exploring best practices in embedded systems, with a focus on operating

'; } 1 2 3 4 5 44 Fix of Broken Range-based for loop Compiler Support for C++23span: best practices for usage Use as argument to function which accepts any contiguous container. Use as return value

code It compiles successfullyWhat is a test? 15 Acceptance Accessibility Active Ad-hoc Age Agile All-pairs Alpha API Application Assertion Automated Backward Compatibility Basis Path Benchmark padded with a custom char") { } REQUIRE(left_pad("abc", 5, '*') == “**abc”);62 Best Practices Testing63 Best Practices Testing Unit Tests should: ‣ Run fast ‣ Be deterministic & reproducible ‣ Be self-contained/ & self-documenting ‣ Use public interfaces ‣ Be focused on one thing (“single assert”)64 Best Practices Testing All tests should: ‣ Be well named ‣ Provide clear and useful feedback ‣ Have a clear reason

Single-Responsibility Principle (SRP) ”A class should have only one reason to change.” (Robert C. Martin, Agile Software Development)18 The Single-Responsibility Principle (SRP) explicit Circle( double rad ”Clients should not be forced to depend on methods that they do not use.” (Robert C. Martin, Agile Software Development)66 The Interface Segregation Principle (ISP) ”Many client specific interfaces Abstractions should not depend on details. Details should depend on abstractions.” (Robert C. Martin, Agile Software Development)Drawing Geometry 84 The Dependency Inversion Principle (DIP) Circle DrawCircle

winrt::impl::make_agile_delegate(struct winrt::Windows::Foundation::AsyncActionCompletedHandler const &)" (??$make_agile_delegate@UAsync

Email: klaus.iglberger@gmx.deContent 3 The Exception Situation How Do Exceptions Work Best Practices of Exception Handling When to Use Exceptions (And When Not) How to Use Exceptions The Exception Refactor Non-Exception-Safe CodeContent 4 The Exception Situation How Do Exceptions Work Best Practices of Exception Handling When to Use Exceptions (And When Not) How to Use Exceptions The Exception           Content 23 The Exception Situation How Do Exceptions Work Best Practices of Exception Handling When to Use Exceptions (And When Not) How to Use Exceptions The Exception

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: . $ conan list * Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: . $ conan list * Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: . $ conan list * Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a

contains things like the FAQ, a very important section about general guidelines, good practices and bad practices, videos from conference talks, etc. Features in this documentation might be labeled as: $ conan list "*" Local Cache pkg pkg/1.0 pkg/1.1 pkg/1.2 pkg/1.3 pkg/1.4 pkg/1.5 Note: Best practices • We could try to use something like the branch name or the commit as the version number. However recipes, recipes can only require down to the recipe revision as we defined above. Warning: Best practices Having more than 1 package revision for any given recipe revision + package_id is a smell or a