s.palanivel rajan wrote:these are the techniques which are not allowed in java but allowed in c++
Pointers
Thank the gods, pointers are how you program in assembly language. They are the source of untold bugs.
s.palanivel rajan wrote:Structures & unions
While technically correct, a java Class is the same as a 'struct' if you don't have any functions.
s.palanivel rajan wrote:Operator overloading
This was popular in languages designed in the 70s, Ada, C++, etc. And the example was always dealing with Strings or Complex numbers.
The problem is, that a decent language should have Strings (and probably Complex) build in, and when you have that, then the obvious uses of operator overloading are rare.
s.palanivel rajan wrote:Multiple inheritance
The bain of my existence when I was a C++ developer
s.palanivel rajan wrote:Goto operator
GOTO considered dangerous. Was true when Djkistra wrote it, and is still true today
s.palanivel rajan wrote:Automatic type conversion
Actually, Java has this for some cases. Strict language designs discourage it.
s.palanivel rajan wrote:Destructors
another huge source of bugs, handling destuctors properly with exceptions is a real challange.
s.palanivel rajan wrote:Unsigned integers
I don't see this as a problem, but not having unsigned byte data is a pain for crypto code