Modernize your C++ code

#1

Post by StylifyYourBlog » Sat, Jan 31, 2015, 5:25 PM UTC

Re: Modernize your C++ code

#2

Post by jbHawk » Sat, Jan 31, 2015, 6:07 PM UTC

I'm really impressed with this tooling. Effectively Resharper for C++. There's a huge market opportunity for C++ tooling.

Re: Modernize your C++ code

#3

Post by huhtenberg » Sat, Jan 31, 2015, 6:41 PM UTC

I see no tangible reason to do this. I mean, all of this is nice, but it's just messing with the working codebase for the sake of messing with it.

Re: Modernize your C++ code

#4

Post by JSno » Sat, Jan 31, 2015, 7:02 PM UTC

if c++ initially came out with c++11 syntax and features. It might be a good language. Now. c++ became a monster including so many different styles, conventions, usages. It's too hard to choose it unless you have legacy system to support.

Re: Modernize your C++ code

#5

Post by glass_of_water » Sat, Jan 31, 2015, 7:37 PM UTC

huhtenberg wrote: post #3

I see no tangible reason to do this. I mean, all of this is nice , but it's just messing with the working codebase for the sake of messing with it.

More maintainable and idiomatic code.

Re: Modernize your C++ code

#6

Post by eps » Sat, Jan 31, 2015, 7:46 PM UTC

jbHawk wrote: post #2

I'm really impressed with this tooling. Effectively Resharper for C++. There's a huge market opportunity for C++ tooling.

How's your astroturfing day going so far?

Re: Modernize your C++ code

#7

Post by yaur » Sat, Jan 31, 2015, 7:56 PM UTC

glass_of_water wrote: post #5

huhtenberg wrote: post #3

I see no tangible reason to do this. I mean, all of this is nice , but it's just messing with the working codebase for the sake of messing with it.

More maintainable and idiomatic code.

Generated code is unlikely to be more maintainable.

Re: Modernize your C++ code

#8

Post by huhtenberg » Sat, Jan 31, 2015, 8:00 PM UTC

glass_of_water wrote: post #5

huhtenberg wrote: post #3

I see no tangible reason to do this. I mean, all of this is nice , but it's just messing with the working codebase for the sake of messing with it.

More maintainable and idiomatic code.

What makes you think that this "modernization" will make it more maintainable, leave alone more idiomatic?

Re: Modernize your C++ code

#9

Post by makecheck » Sat, Jan 31, 2015, 8:33 PM UTC

huhtenberg wrote: post #3

I see no tangible reason to do this. I mean, all of this is nice , but it's just messing with the working codebase for the sake of messing with it.

Well to take the very first example from the article, adding "override" keywords: that improves your chances of avoiding bugs during normal maintenance. Have you never seen a base class that had more than a few derived classes, some of which may be in places you didn't even know about? Now imagine tweaking a base class method's signature slightly, and missing one of those derived classes somewhere, which had been trying to keep its copy of the signature in sync. Before it was overriding, now it is just a new method; there's a bug that "modernization" would have caught for you.

Re: Modernize your C++ code

#10

Post by fsloth » Sat, Jan 31, 2015, 8:45 PM UTC

huhtenberg wrote: post #3

I see no tangible reason to do this. I mean, all of this is nice , but it's just messing with the working codebase for the sake of messing with it.

I do not see why you were downvoted. I earn my living writing C++ for a living for mission critical CAD applications and I cannot imagine me or any one of my colleagues use an automatic converter.

C++11 is nice. For new code. I see no reason to use this for old, working code.