The C++ language is evolving. A bunch of new features were added to it in 2011, and some more are coming in 2014. Gradually, compilers are adding support for them. And programmers can now start exploring these features, learning both their power and their limitations.
In this series of articles I document what I learned in my own explorations of the language, both on my own and with the help of others.
10 Sep 2013
The little tail that could
where I go over ogonek's API design
11 Mar 2013
Beating overload resolution into submission
where Xeo brings order into the SFINAE chaos
25 Feb 2013
Even more type traits
where I showcase more nice traits
18 Feb 2013
Size matters, part 4
where I finally implement the tuple class
11 Feb 2013
To SFINAE or not to SFINAE
where I wonder if SFINAE is really needed
09 Dec 2012
Size matters, part 3
where I abuse overload resolution for fun and profit
02 Dec 2012
Size matters, part 2
where I sort types for optimal layout
15 Aug 2012
Rule of Zero
where I rediscover the Single Responsibility Principle
06 Jul 2012
Size matters, part 1
where I explore the layout of tuples
05 Jun 2012
Some pitfalls with forwarding constructors
where I find that you can copy without invoking the copy constructor
01 Jun 2012
where I fix enable_if
29 May 2012
More type traits
where I showcase cool traits
27 May 2012
Handling dependent names
where I get rid of typename
Writing is a crucial part of almost all human cultures. The vast diversity in human cultures has lead to the use of numerous writing systems. Unicode is an attempt at making it possible for programmers to represent and handle text in all of those writing systems.
I got curious about Unicode around June 2012, after several discussions about the sad state of affairs in C++. I started by writing a simple set of encoders and decoders just for show, but got progressively more and more interested in the subject. Eventually I found myself writing what I now intend to turn into a serious library for handling Unicode.
This series of posts explains some of the motivations, problems, and design decisions involved in the development of ogonek, a Unicode library with a C++ feel.
I learned to ride a bicycle when I was more than twelve years old. Some years later I moved to the city and kind of forgot about my bicycle. Even more years later I moved to Berlin and—oh my, bicycles everywhere.
Eventually I acquired a bicycle to displace myself across Berlin and with that came a new-found liking for cycling.
And then I decided to experiment a bit with writing about my cycling expeditions.
I have written some C++ libraries that others might find useful. The documentation for those libraries can be found here.
- ogonek » Unicode using C++ idioms [prerelease docs];
- and more coming soon?
Over time I produce other things worth of putting up here. These are some of those things.