Programmer Humor

19589 readers

442 users here now

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.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

[email protected]

540

You can certainly change it. But should you? (lemmy.ml)

submitted 7 months ago by [email protected] to c/[email protected]

62 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 66 points 7 months ago (1 children)

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.

[–] [email protected] 27 points 7 months ago (1 children)

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

[–] [email protected] 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).

[–] [email protected] 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.

[–] [email protected] 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