Should probably fix that given we’ve been out of IPv4 for over a decade now and v6 is only becoming more widely deployed

This sums up how I feel nicely. No issues with parens…but whitespace…fuck that shit

It’s actually not. Objective-C is a superset of C. C++ is not. It’s MOSTLY compatible…but it’s not a superset. See the restrict keyword, or the need for casting to and from void*, or the inability to name variables new or delete, or class, or this. I can’t count how many C projects I have which use this as a variable name that WILL NOT compile as C++…or the need for extern C to call C ABI code…in no way is it a superset

EDIT: lol, you can downvote me if you want but I think you need to lookup what a superset is

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

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 really wish more projects would use .hpp to differentiate from C headers. It’s really annoying to have a single header extension blend across two incompatible languages.