Explore >> Select a destination
|
You are here 
|
bartoszmilewski.com | ||
| | | | |
dreamrunner.org
|
|
| | | | | C++11 Memory Model and Atomic | |
| | | | |
darkcoding.net
|
|
| | | | | Solvitas perambulum | |
| | | | |
stefansf.de
|
|
| | | | | [AI summary] The provided text discusses the misuse of the `volatile` keyword in C programming and its inability to address concurrency and memory ordering issues. It explains that `volatile` ensures that compiler optimizations do not remove accesses to variables, but it does not guarantee memory visibility or prevent hardware reordering. The text highlights that `volatile` is only suitable for specific use cases like memory-mapped I/O, and that for thread-safe operations, atomic types and memory barriers are necessary. It also covers examples of how `volatile` can lead to incorrect behavior in multi-threaded programs and how C11's memory model and atomic operations provide a more robust solution. | |
| | | | |
www.morling.dev
|
|
| | | The ResourceBundle class is Java's workhorse for managing and retrieving locale specific resources, such as error messages of internationalized applications. With the advent of the module system in Java 9, specifics around discovering and loading resource bundles have changed quite a bit, in particular when it comes to retrieving resource bundles across the boundaries of named modules. In this blog post I'd like to discuss how resource bundles can be used in a multi-module application (i.e. a "modular mo... | ||
