Prior to its deletion for reasons unknown, there was a post that (reading between the lines) was calling you out on the term &quot;access&quot;, which doesn&#x27;t appear to encompass writing: <a href="http:&#x2F;&#x2F;port70.net&#x2F;~nsz&#x2F;c&#x2F;c11&#x2F;n1570.html#3.1" rel="nofollow">http:&#x2F;&#x2F;port70.net&#x2F;~nsz&#x2F;c&#x2F;c11&#x2F;n1570.html#3.1</a><p>I&#x27;d class that as a valid quibble, if my interpretation is correct, but a quibble nonetheless. The general intent is clear enough from the standard, I think: <a href="http:&#x2F;&#x2F;port70.net&#x2F;~nsz&#x2F;c&#x2F;c11&#x2F;n1570.html#6.7.2.1p18" rel="nofollow">http:&#x2F;&#x2F;port70.net&#x2F;~nsz&#x2F;c&#x2F;c11&#x2F;n1570.html#6.7.2.1p18</a><p>Further reading on the subject of undefined behaviour (apropos of nothing in particular): <a href="http:&#x2F;&#x2F;port70.net&#x2F;~nsz&#x2F;c&#x2F;c11&#x2F;n1570.html#3.4.3p1" rel="nofollow">http:&#x2F;&#x2F;port70.net&#x2F;~nsz&#x2F;c&#x2F;c11&#x2F;n1570.html#3.4.3p1</a>, <a href="http:&#x2F;&#x2F;robertoconcerto.blogspot.co.uk&#x2F;2010&#x2F;10&#x2F;strict-aliasing.html" rel="nofollow">http:&#x2F;&#x2F;robertoconcerto.blogspot.co.uk&#x2F;2010&#x2F;10&#x2F;strict-aliasin...</a>, <a href="https:&#x2F;&#x2F;groups.google.com&#x2F;forum&#x2F;#!msg&#x2F;boring-crypto&#x2F;48qa1kWignU&#x2F;o8GGp2K1DAAJ" rel="nofollow">https:&#x2F;&#x2F;groups.google.com&#x2F;forum&#x2F;#!msg&#x2F;boring-crypto&#x2F;48qa1kWi...</a>, <a href="http:&#x2F;&#x2F;blog.metaobject.com&#x2F;2014&#x2F;04&#x2F;cc-osmartass.html" rel="nofollow">http:&#x2F;&#x2F;blog.metaobject.com&#x2F;2014&#x2F;04&#x2F;cc-osmartass.html</a>