- flat set/map - multi_index - static_vector (called SmallVector in LLVM) - bimap - intrusive containers - various from Boost.Heap
724 karma · joined July 24, 2010
- flat set/map - multi_index - static_vector (called SmallVector in LLVM) - bimap - intrusive containers - various from Boost.Heap
The first mayor library to use this syntax was Boost.Range and it is now being proposed as the syntax of standard ranges.
Only some states decided to demand tuition for their universities in 2006 (some later) and most quickly stopped again after a few years.
As for Germany: almost all public Universities still take fees (usually around 100 Euros per semester, tax refundable). Tuition was a new thing and is what has been abandoned again.
You might be interested in metaparse [1] which can greatly simplify compile time parsing of strings but has a very steep learning curve.
And you are also forgetting that this is done to prevent the spread of life-threatening diseases for which we do not have a working treatment yet and the emergence of new diseases of that kind.
Those are hard problems. Hunger in the first world is not (we already overproduce any kind of food) and even if meat would become scarce we could just use a fraction of the resources which are now used to raise livestock to feed ourselves.
[1]: http://www.drdobbs.com/architecture-and-design/so-you-want-t...
[1]: http://www.artsjournal.com/slippeddisc/2012/01/exclusive-how...
As long as there is only one compiler and no guarantee that you will not have to change everything once again as standardization is complete no one is going to touch a large cross-platform codebase and add module support.
While it seems that everybody has almost the same idea how modules should look as part of the language almost no one can agree on how they should be specified or what part of a module should actually be specified at all.
I also think that a modern language that uses includes instead of modules is just outright insane.
I'm sure there are exceptions to this, but they are hard to find and universities aren't entirely to blame for it. Some parts of software engineering move fast and there is a justified fear to teach students things that will be useless by the time they graduate. So the focus is more on laying a solid ground-work.
> "You just don't in the 21st Century behave in 19th Century fashion by invading another country on completely trumped-up pretext," Mr Kerry told the CBS program Face the Nation.
Coming from a US official this sounds very much like a bad joke.
Imagine a different scenario: One of the the less stable EU members with a US base (basically all of them) has a revolution and the winning party plans to get rid of the US military bases. What is going to happen? Is the US just going to give up on it? Does it depend on the importance of the base (think Rammstein)? I'm sure no one doubts that the US would intervene in some way.
Still, elisp is elisp is elisp and there is no getting around that fact. The last Common Lisp rewrite/transformation has, AFAIK, stalled. 'cl is still not welcome in core packages. Just staying with the language and dealing with its quirks has proven very effective and I think this is in a large part due the flexibility of being a Lisp. It might be the wrong language for text-processing, but is the right language for ancient software that tries to stay recent.
> text display, scripting, styling
The only thing that really matters is scripting. Every serious editor has solved displaying text and styling since ages and those two points aren't even that important in programming languages. All you want is a syntax aware highlighting. Maybe underlines and a little bold here and there.
Scripting is the really hard part. There are many flavors, languages, APIs to chose from. Just because you now can script things in <hip-language-of-the-day>, the problem isn't solved. My editor uses a lisp dialect and I'm perfectly happy with it, not because of the language choice but the APIs and amount of integration.
One thing that is incredibly important for text editors is speed: something web engines are notoriously bad at.
I still can't believe that decision makers actually believe that customers want that. Sure, it makes for great bullet points on the packaging, but most consumer in the lower segment just want something that is familiar to all the other stuff they have. Things you will never hear an Android user say: "That Samsung Whatever Cloud App is really useful.", "That second App Store of my carrier is full with great Apps.", and "I wish those buttons were even more different from my old Android phone".