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.

[–] humbletightband@lemmy.dbzer0.com 27 points 7 months ago (1 children)

I will not tell my kids regular scary stories. I will tell them about embedded systems

[–] suzune@ani.social 22 points 7 months ago* (last edited 7 months ago) (2 children)

When you program embedded you'll also dereference NULL pointers at some point.

More...

Some platforms can have something interesting at memory address 0x0 (it's often NULL in C).

[–] Scoopta@programming.dev 14 points 7 months ago

In amd64/x86 kernel space you can dereference null as well. My hobby kernel keeps critical kernel structures there XD.

[–] humbletightband@lemmy.dbzer0.com 2 points 7 months ago* (last edited 7 months ago)

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