Wolf480pl on Nostr: nprofile1q…pa33k tedu in the example I gave, the &p->y is, by definition, just ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq3t0vxvx8llrdglujal9hh93mtnl7wac0mxqd7xtdyryc4per8q4qhpa33k (nprofile…a33k) tedu (nprofile…pt5e) in the example I gave, the &p->y is, by definition, just pointer arithmetic.
So it won't segfault.
It might signed-overflow, but if the binary representation of null is zero, it probably won't.
But if optimizations are on, the compiler is free to use that statement as an excuse to remove the null check. Because if I did pointer arithmetic on p, then surely p can't be null, right?
So it won't segfault.
It might signed-overflow, but if the binary representation of null is zero, it probably won't.
But if optimizations are on, the compiler is free to use that statement as an excuse to remove the null check. Because if I did pointer arithmetic on p, then surely p can't be null, right?