I backed it out, will try to fix differently.
Martin
On Sun, Jul 19, 2015 at 11:13:48PM +0200, Kamil Rytarowski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19.07.2015 20:56, Joerg Sonnenberger wrote:
On Thu, Jul 16, 2015 at 12:12:27PM +0200, Kamil Rytarowski wrote:
The C standard permits memcpy(3) to affect errno(2).
More
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19.07.2015 20:56, Joerg Sonnenberger wrote:
On Thu, Jul 16, 2015 at 12:12:27PM +0200, Kamil Rytarowski wrote:
The C standard permits memcpy(3) to affect errno(2).
More like it hasn't explicitly ruled it out. That might or might
not be seen
On Thu, Jul 16, 2015 at 12:12:27PM +0200, Kamil Rytarowski wrote:
The C standard permits memcpy(3) to affect errno(2).
More like it hasn't explicitly ruled it out. That might or might not be
seen as an oversight, but pretty much any compiler uses memcpy(3) under
the assumption that it does not.
