That's a bit too much. I think at least for mixins and to implement what other languages call interfaces it is ok.
For more than that it is better not. -- Paulo "Alex Rønne Petersen" <xtzgzo...@gmail.com> wrote in message news:j3la80$lh4$1...@digitalmars.com... > On 31-08-2011 10:55, Lars T. Kyllingstad wrote: >> I am starting in a new job on Monday, in which the primary programming >> language is C++. For the past four years I've had the privilege of being >> able to use D both professionally and privately, and consequently my C++ >> skills (which were intermediate to begin with) are now a bit rusty. >> >> Since I know there are a lot of extremely talented C++ programmers in the >> D community, I thought I'd ask here for some tips. >> >> Firstly, can you think of any pitfalls to avoid? In particular, I am >> interested in the ones that stem from subtle differences between the two >> programming languages. I believe I am already aware of the most obvious >> stuff (such as for example array bounds checking, or lack thereof). >> >> Secondly, can you recommend a good C++ book? I am looking for one that >> targets an audience with good general programming skills, and which can >> act as a language reference. >> >> Hopefully, my adventures in the world of C++ will give me new >> perspectives on things, allowing me to contribute even better to the >> improvement of D. ;) >> >> -Lars > > Whatever you do, avoid multiple inheritance like the plague. It will bite > you, especially if you use pointers. > > - Alex