Yes, a 2D raster library is exactly what C++ developers need.

Now excuse me while I go back waiting for my +1 hour compile to finish because the #include model is a mess and since we keep getting more and more templates, compilation time keeps increasing.

FYI the first sentence was sarcasm.

By the way, I fully agree with Bregma

Yes, a 2D raster library is exactly what C++ developers need.

Now excuse me while I go back waiting for my +1 hour compile to finish because the #include model is a mess and since we keep getting more and more templates, compilation time keeps increasing.

FYI the first sentence was sarcasm.

By the way, I fully agree with Bregma

yeah...

this is one area where either using C or at least not using the C++ libraries, offers an advantage:

language features or not, compile times are a little less painful (though still painful, as is a natural cost of any non-trivial codebase).

though, granted, at this point "mostly using plain C" is often considered a kind of craziness, but whatever...

otherwise, hell, maybe nice if some semantics could be introduced to allow making precompiled headers and similar not suck, along with partly standardizing their behavior, ... ? (so then you can write generic code using precompiled-header magic and have it work across compilers).

possibly, sort of like "#include_once" or similar, but with some extended semantics (such that a compiler "may" do PCH magic, otherwise it is included as normal...).

well, among other things...

They are developing a better build system for C++. They're calling it the "module" system.

They are developing a better build system for C++. They're calling it the "module" system.

But the ISO committee is making zero (or near-zero) effort towards it. It mostly comes from the people working on Clang and c++ devs working on real projects who are fed up of the language's lack of scalability.

Though there is actual developement on the practical area, this is one of the most exciting features c++ and is left in the back burner by the the guys who decide what becomes standard. I would love to be proven wrong.

All of C++ is worked on by people in their spare time, or are paid to work on it by their employers. More than half the people on the committee seem to be working as engineers for large software companies.

Clang? Alot of the effort there comes from people employed by Apple, afaik.

See here:

• SG1, Concurrency: Hans Boehm (HP). Concurrency and parallelism topics.
• SG2, Modules: Doug Gregor (Apple). Work on possible refinement or replacement for the header-based build model.
• SG3, File System: Beman Dawes (Boost). Work based on Boost.Filesystem v3.
• SG4, Networking: Kyle Kloepper (Riverbed). Networking related libraries, including sockets and HTTP.
• SG5, Transactional Memory: Michael Wong (IBM). Exploring transactional memory constructs for potential future addition to the C++ language.
• SG6, Numerics: Lawrence Crowl (Google). Numerics topics, including but not limited to fixed point, decimal floating point, and fractions.
• SG7, Reflection: Chandler Carruth (Google). Initially focusing on compile-time reflection capabilities.
• SG8, Concepts: Matt Austern (Google). Near-term focus is on a convergence between the static if proposals and the parameter-type-constraints subset of concepts.
• SG9, Ranges: Marshall Clow (Qualcomm). How to update the standard library with a range concept rather than naked iterator pairs, including containers and range-based algorithms.
• SG10, Feature Test: Clark Nelson (Intel). Investigation into whether and how to standardize a way for portable code to check whether a particular C++ product implements a feature yet, as we continue to extend the standard.
• SG11, Databases: Bill Seymour (USPS). Database-related library interfaces.
• SG12, Undefined and Unspecified Behavior: Gabriel Dos Reis (Microsoft). A systematic review to catalog cases of undefined and unspecified behavior in the standard and recommend a coherent set of changes to define and/or specify the behavior.
• SG13, Graphics: Herb Sutter (Microsoft). Investigation into possible standardization of a “2D Lite” simple graphics library.