Deep C and C++ (2011)

Post by caf » Wed, Oct 23, 2013, 7:36 AM UTC

aidenn0 wrote: post #4

Heh, and they didn't even get into the aliasing rules. In embedded software, life would be a lot easier if I could hit every engineer who wants to type-pun without a union in the head with the ISO standard. For this reason, a lot of compilers have options to not strictly enforce the aliasing rules [edit] Also C and C++ are both permitted to reorder structs, it's just that they don't because that's the easiest way to…

  A structure type describes a sequentially allocated
  nonempty set of member objects (and, in certain
  circumstances, an incomplete array), each of which 
  has an optionally specified name and possibly 
  distinct type.

  If the objects pointed to are members of the same
  aggregate object, pointers to structure members 
  declared later compare greater than pointers to 
  members declared earlier in the structure,…

Post by hamidr » Wed, Oct 23, 2013, 7:39 AM UTC

xerophtye wrote: post #17

pacaro wrote: post #9

I've been a C developer (among other things) for about 20 years or so, but I've always described my C++ skills as being "in the C with objects" range, I might have to change that to being "nearly in the C with objects" range.

Yep, with C and C++ , you can't really say you are an expert.

Post by jmgao » Wed, Oct 23, 2013, 7:45 AM UTC

aidenn0 wrote: post #4

Heh, and they didn't even get into the aliasing rules. In embedded software, life would be a lot easier if I could hit every engineer who wants to type-pun without a union in the head with the ISO standard. For this reason, a lot of compilers have options to not strictly enforce the aliasing rules [edit] Also C and C++ are both permitted to reorder structs, it's just that they don't because that's the easiest way to…

    Nonstatic data members of a (non-union) class declared without an
    intervening access-specifier are allocated so that later members
    have higher addresses within a class object. The order of allocation
    of nonstatic data members separated by an access-specifier is unspecified (11.1)

    struct foo {
        int a;
    public:
        int b;
    }

Post by dmak » Wed, Oct 23, 2013, 7:49 AM UTC

raverbashing wrote: post #18

deckiedan wrote: post #13

It is interesting looking at the 'deep' issues of programming languages. This kind of ties in with the "Don't ask me maths questions..." post a few days ago. There really is a lot more to programming than just algorithms, UI design or syntax.

Yes, this worries me. Especially today some people think "great programmers" are the ones who knows all the "fashionable" tools and frameworks, wants to abstract everything (god help him if he install vim in his test environment without a fab file that configures chef) and maybe worships Uncle Bob Knowing how to use Redis is cool, do you know what's even cooler? Being able to write it (or at least knowing how it work…

Post by dmak » Wed, Oct 23, 2013, 7:51 AM UTC

deckiedan wrote: post #13

It is interesting looking at the 'deep' issues of programming languages. This kind of ties in with the "Don't ask me maths questions..." post a few days ago. There really is a lot more to programming than just algorithms, UI design or syntax.