News for hackers. Stuff that matters.
Re:GCC Undefined Behavior Sanitizer – Ubsan by 3ifbyw on Thursday October 16, 2014 @05:24PM (#8467843)
s/ a while/ever/
Re:GCC Undefined Behavior Sanitizer – Ubsan by pjmlp on Thursday October 16, 2014 @05:50PM (#8468001)
I am pretty aware that C and C++ are going to outlive me, but that doesn't mean they will be the systems programming languages of choice until the Sun ceases to exist.

Being someone that enjoys C++, doesn't mean I have to agree with all design decisions.

Neither will I reject to use C, if that is what the customer pays me for, even if I dislike it. Professionalism comes before personal opinions.

Re:GCC Undefined Behavior Sanitizer – Ubsan by Animats on Thursday October 16, 2014 @05:31PM (#8467885)
Not necessarily. Even the C++ committee now accepts that most of the C++ code that will ever be written has already been written.
Re:GCC Undefined Behavior Sanitizer – Ubsan by CJefferson on Thursday October 16, 2014 @06:27PM (#8468200)
I have no idea where you get the claim from. I know many members of the C++ committee, and they expect new C++ to continue to be written, else why would they bother with C++11/14/17?
Re:GCC Undefined Behavior Sanitizer – Ubsan by Dylan16807 on Thursday October 16, 2014 @08:36PM (#8468765)
But do they expect more new billions of lines of C++ to be written than have ever been written before?
Re:GCC Undefined Behavior Sanitizer – Ubsan by crpatino on Thursday October 16, 2014 @05:57PM (#8468049)
Could you please clarify? Do you mean that more than 50% of the eventual total lines of C++ have already been written as of today (Peak C++, anyone)?

Or do you mean that a very large percentage of eventual lines of C++ to be written in the future are expected to be endless variations and downright repetitions of the total C++ lines been written as of today?