c++ - casting object addresses to char ptrs then using pointer math on them -


according effective c++, "casting object addresses char* pointers , using pointer arithemetic on them yields undefined behavior."

is true plain-old-data? example in template function wrote long ago print bits of object. works splendidly on x86, but... portable?

#include <iostream>  template< typename type > void printbits( type data ) {     unsigned char *c = reinterpret_cast<unsigned char *>(&data);      std::size_t = sizeof(data);     std::size_t b;      while ( i>0 ) {         i--;         b=8;         while ( b > 0 ) {             b--;             std::cout << ( ( c[i] & (1<<b) ) ? '1' : '0' );         }     }     std::cout << "\n"; }  int main ( void ) {     unsigned int f = 0xf0f0f0f0;     printbits<unsigned int>( f );     return 0; }

it not portable. if stick fundamental types, there endianness , there sizeof, function print different results on big-endian machines, or on machines sizeof(int) 16 or 64. issue not pods fundamental types, structs may pod, too.

pod struct members may have internal paddings according implementation-defined alignment rules. if pass pod struct:

struct paddedpod { char c; int i; }

your code print contents of padding, too. , padding different on same compiler different pragmas , options.

on other side, maybe it's wanted.

so, it's not portable, it's not ub. there standard guarantees: can copy pods , array of char or unsigned char, , result of copying via char buffer hold original value. implies can safely traverse array, function safe. nobody guarantees array (or object representation) of objects same type , value same on different computers.

btw, couldn't find passage in effective c++. quote it, pls? say, if part of code contains lots of #ifdef thiscompilerversion, makes sense go all-nonstandard , use hacks lead undefined behavior, work intended on compiler version pragmas , options. in sense, yes, casting char * leads ub.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more