Habrahabr loveplusplus dating Cam chati
Deprecate the bad stuff (see: throw specifiers, auto_ptr).
Write tools that help people program in the modern subset (see: clang modernize).
It's grueling, but C as a whole is better for it, IMO. If you had to name one or two changes in the C 11/14 Standard that are the most important, which ones would you choose?
Is there any chance that some day a version of C with little or no backward compatibility will be released? Again, my perspective is skewed here by my role as a library developer.
In it's place, I would prefer an AST-based, hygenic macro processor.
So, for me, online dating was a good way to meet guys without pressure.Many people are asking for some standard repository like in some other languages. Is there a need for it and how soon the C community can make it possible? Together with tooling, it's the biggest obstacle to adoption C has today, IMO. It's the kind of hard, boring, inglorious work that tends not to get picked up by volunteers. I haven't tried CLion yet, but Eclipse was too awful for words the last time I tried it (which admittedly was a long time ago).Some clever folks have tried to solve this problem, with limited success to date. Many people may think that C is terrible, actually, but they’re still using it, and it’s the main language used in their development. What do you think about that and couldn’t C be used more efficiently for these applications. These days, I'm hearing a bit more about teams writing the bulk of their mobile application logic in C for the sake of portability. I've heard some positive buzz, but I haven't looked into it. Emacs/vim/gdb feels like banging rocks together when the rest of the world is at cruising speed.Is there something that can have a negative effect? They're powerful, but they're just too hard to use correctly, and too easy to use incorrectly. It's possible to write clean, simple, beautiful C code these days.
My style has evolved such that I use them very sparingly and only in ways that I can feel confident about. Not even the Committee can agree on how and where to use it. As for evolving a complex language like C : Make changes that increase uniformity (see: uniform initialization) and give people simpler, safer ways to do complicated, error-prone things (see: auto, range-for, smart pointers).How do you think the decision should be made about what language to use in a large projects? Do you think that it’s bad for C that it’s rarely used on mobile devices? I'm dumbfounded that C isn't used more heavily on mobile. The prospect of maintaining parallel codebases in different languages is just too awful to consider. (Cue the angry trolls telling me what a Luddite I am for disparaging Emacs/vim/whatever.) How did you convince the Committee that the Ranges library is important?