JPDev@programming.dev to Programmer Humor@programming.dev · edit-22 years agoDo you know who can help?programming.devimagemessage-square9linkfedilinkarrow-up111arrow-down11
arrow-up110arrow-down1imageDo you know who can help?programming.devJPDev@programming.dev to Programmer Humor@programming.dev · edit-22 years agomessage-square9linkfedilink
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up1·2 years agoI don’t think I’ve ever explicitly gone four deep. Two is common enough, and three happens on some rare occasions, but four seems like sheer madness.
minus-squareEphera@lemmy.mllinkfedilinkarrow-up0·2 years agoDumb question, but when would you need two deep? Is it when you store a pointer as a field in a struct? If so, isn’t that a massive footgun, because the pointer might go invalid at any point? 🫠
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up1·2 years agoPointers to arrays or arrays of pointers are common examples. Your pointers won’t just magically become invalid. You gotta fuck 'em up first.
I don’t think I’ve ever explicitly gone four deep. Two is common enough, and three happens on some rare occasions, but four seems like sheer madness.
Dumb question, but when would you need two deep? Is it when you store a pointer as a field in a struct?
If so, isn’t that a massive footgun, because the pointer might go invalid at any point? 🫠
Pointers to arrays or arrays of pointers are common examples.
Your pointers won’t just magically become invalid. You gotta fuck 'em up first.