44 karma · joined December 8, 2016
"If there is no null byte among the first n bytes of src, the string placed in dest will not be null-terminated."
So copying sizeof(dest)-1 will not append a NULL byte as the author implies. You'll have to do that manually.
People who think "goto" is evil should also give up the other jump statements: continue, break, and return (and also switch, though its not listed as a jump instruction in the C standard, at least not in '89 or '99).
You can see some contradictions in the paper regarding goto. For example, they state that deep nesting should be avoided, but goto should be avoided as well, even though one benefit of using goto is to limit nesting depth. From the Linux Kernel coding style doc: - unconditional statements are easier to understand and follow - nesting is reduced - errors by not updating individual exit points when making modifications are prevented - saves the compiler work to optimize redundant code away ;)
Also, does "in a dream" count?
Nevermind, found a link that talked about the paper. They used a US 5¢ coin, a nickel which has a flat edge and I think the thickest edge out of all (common?) US coins. At least it has the thickest edge to face ratio in terms of width.
A coin with rounded edges won't land on its edge 1 out of 6000 tosses. A coin with a flat edge that is thicker than either of its faces (or just thick in general; doesn't have to be thicker than the faces) will land on its edge a great deal more often.
Also, a coin with a heavier "tails" side will more often land on heads in a spin.
I guess I should read the paper. Maybe it clarifies.
FittedCloud is a small start-up that does automatic cloud resource optimization. They post regularly and go into topics ranging from technical details of machine learning to cost optimization for AWS resources (EBS, EC2, DynamoDB, etc).
As far as I can tell, they are the only company around that can automatically scale up and down EBS resources in a way that the customer only pays for what he or she uses, rather than paying for over-provisioned, unused storage...all without downtime or performance hic-cup. These guys know a lot about the cloud and storage.