Linked by Thom Holwerda on Mon 13th Aug 2007 17:57 UTC
Thread beginning with comment 263337
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Parallel programming you say. Let's see: OpenMP auto-parallelization works with C/C++/Fortran (yes, Fortran!). Intel's new TBB library (low level lock-free/fine grained locks algorithms and data structures) works with C++. SIMD (SSE, 3dNow, AltiVec) based parallelization -- languages with inline assembly: C/C++. Doesn't sound like farce to me.






Member since:
2007-04-20
There have been a million similar discussions on the net C vs C++ vs Java, etc. Programming language is a tool and you need better tools to create more complex software. Programmers have been using the same old tools for decades and the quality of software they create is abysmal. New languages/methodologies need to reflect the fact that the future systems need to support fine grained multithreading if they are to effectively utilise multicore CPUs with UMA or NUMA hardware configurations. Parallel programming is a difficult challenge and the current programming languages are not suited for such tasks.
"Next generation C++" sounds like a farce to me. I think in order to get the optimal performance and rigidity, the hardware, system software and development tools, need to be designed as a unity, with references to one another. Creating a programming language in near vacuum will not achieve the flexibility required for high-performance, reliable and complex software.