I mean, it&#x27;s definitely a neat way to optimize comparisons for the CPU&#x27;s word size. The problem is with completely unexplained things like:<p><pre><code>  #define ONES ((size_t)-1&#x2F;UCHAR_MAX)
</code></pre>
Reading through the loop, it seems as though it will create, e.g., 0x01010101 for a 32-bit machine with 8-bit bytes. And sure enough, if you calculate ((2^32)-1)&#x2F;255 that&#x27;s exactly what you get. But I never would&#x27;ve known that without going through the code and proving to myself that the definitely of ONES actually makes sense.<p>If you write code like this and there are never any bugs then fine, I guess. But there will bugs.