The Picard Maneuver@lemmy.worldM to memes@lemmy.world · 2 days agoMaking a difference, one date at a time.lemmy.worldimagemessage-square106linkfedilinkarrow-up1945arrow-down112
arrow-up1933arrow-down1imageMaking a difference, one date at a time.lemmy.worldThe Picard Maneuver@lemmy.worldM to memes@lemmy.world · 2 days agomessage-square106linkfedilink
minus-squarelime!@feddit.nulinkfedilinkarrow-up1·23 hours agodepends on the area you’re working in. it’s a pretty important distinction in embedded software.
minus-squareSorryQuick@lemmy.calinkfedilinkarrow-up3·14 hours agoWhy? I’ve worked as an embedded dev for a few years and nobody in my team cared what it was called.
minus-squarelime!@feddit.nulinkfedilinkarrow-up1·13 hours agobecause making sure offsets are correct come up a lot when you’re memory-mapping IO.
minus-squareSorryQuick@lemmy.calinkfedilinkarrow-up2·10 hours agoRight but whether they’re correct or not doesn’t depend on the name you use. Every programmer worth his name knows arrays start at offset zero even if you don’t call it that.
minus-squarelime!@feddit.nulinkfedilinkarrow-up1·edit-28 hours agoexcept if you use lua. …which doesn’t have arrays, but still.
depends on the area you’re working in. it’s a pretty important distinction in embedded software.
Why? I’ve worked as an embedded dev for a few years and nobody in my team cared what it was called.
because making sure offsets are correct come up a lot when you’re memory-mapping IO.
Right but whether they’re correct or not doesn’t depend on the name you use. Every programmer worth his name knows arrays start at offset zero even if you don’t call it that.
except if you use lua.
…which doesn’t have arrays, but still.