Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.c++.moderated    |    Moderated discussion of C++ superhackery    |    33,346 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 33,096 of 33,346    |
|    Edward Rosten to Seungbeom Kim    |
|    Re: compilers, endianness and padding    |
|    28 May 13 04:12:05    |
      From: firstname.dot.lastname@googlemail.com              On Sat, 25 May 2013 17:34:38 -0600, Seungbeom Kim wrote:              > On 2013-05-24 05:28, Edward Rosten wrote:       >>       >> Of course, (de)serialising junk is a waste of bandwidth and       >> storage, so it wouldn't be ideal, but I don't see that it would be       >> too much of a problem otherwise.       >       > For one thing, trying to read uninitialized junk results in       > undefined behavior, and you cannot get around it because it happens       > automatically.              That doesn't matter: we're talking about something new so the       implementation is free to define it in this case. In practice, if the       memory is mapped in, and not MMIO, then reading as bytes is       harmless. The allocator can know that since it was responsible for       allocating the memory in the first place.              -Ed                     --        [ See http://www.gotw.ca/resources/clcm.htm for info about ]        [ comp.lang.c++.moderated. First time posters: Do this! ]              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca