Explore >> Select a destination
|
You are here 
|
arne-mertz.de | ||
| | | | |
cigix.me
|
|
| | | | | [AI summary] The provided text is a detailed excerpt from the C11 standard, specifically focusing on the C programming language's concurrency and synchronization mechanisms. It outlines the concepts of atomic operations, memory ordering, and the 'happens before' relationship, which are crucial for ensuring correct and predictable behavior in multi-threaded programs. The text also touches on environmental considerations, such as character sets and their representation in source and execution environments. The content is highly technical and intended for developers and language designers familiar with concurrent programming and low-level system interactions. | |
| | | | |
erikmcclure.com
|
|
| | | | | [ 1 · 2 · 3 · 4 · 5 · 6 · 7 ] If you are familiar with C#, you should be familiar with the difference between C#'s struct and class declarations. Namely, a struct is a value type and a class is a reference type, meaning that if you pass a struct to a function, its default behavior is for the entire struct to be copied into the function's parameter, so any modifications made to it won't affect whatever was passed in. | |
| | | | |
quuxplusone.github.io
|
|
| | | | | I love type erasure in C++. But I find every so often I'll be in a conversation with someone, and they'll use the phrase, and they won't mean quite the same thing as I mean, and it'll take a while before we realize that we're talking about completely different ideas. So I think it'll be useful to write down what I mean by the phrase "type erasure" in C++. | |
| | | | |
waspdev.com
|
|
| | | My rant about the famous saying in software development, which is usually attributed to Bjarne Stroustrup. | ||
