541
You can certainly change it. But should you?
(lemmy.ml)
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
It makes more sense if you think of
const
as "read-only". Volatile just means the compiler can't make the assumption that the compiler is the only thing that can modify the variable. Aconst volatile
variable can return different results when read different times.I thought of it more in terms of changing constants (by casting the
const
away). AFAIK when it's notvolatile
, the compiler can place it into read-only data segment or make it a part of some other data, etc. So, technically, changing aconst volatile
would be less of a UB compared to changing a regularconst
(?)const volatile is used a lot when doing HW programming. Const will prevent your code from editing it and volatile prevents the compiler from making assumptions. For example reading from a read only MMIO region. Hardware might change the value hence volatile but you can't because it's read only so marking it as const allows the compiler to catch it instead of allowing you to try and fail.
I will not tell my kids regular scary stories. I will tell them about embedded systems
When you program embedded you'll also dereference
NULL
pointers at some point.More...
Some platforms can have something interesting at memory address0x0
(it's oftenNULL
in C).In amd64/x86 kernel space you can dereference null as well. My hobby kernel keeps critical kernel structures there XD.
I was thinking about telling them how in embedded systems it's a good practice to allocate the memory by hand, having in mind the backlog, but yours will come first