Re: Jumping ship from C++

Quite an interesting thread. I will not talk too much about C++, the last time I used it really (I mean with a real object orientation) for a serious purpose was about 18 years ago. I don't remember so much about it, and I was never an expert in the area anyway. I have continued to use C++ compilers more recently, but more as an implementation of C with additional features that simplified or solved some of the malloc/free/Null_pointer/SegFault/CoreDump etc. memory allocation problems in pure C. And even that subset of C++, I haven't done any of it since 2005 or 2006, I guess (to a certain extent because I had discovered Perl in between and found that it did fit the bill of what I needed far better). Therefore, I am not (or at least no longer) qualified to seriously talk about C++.

But I moved from another OO language (Python) to Perl about 11 years ago, so you might have some interest in what I wrote about two months ago on the subject: Re: Migrating from Perl to other language? Why would someone do that?. Just in case this is not clear, I should say that I am not criticizing OO programming in any way here, I mentioned OO just because it is a common top feature of both C++ and Python.

Comment on Re: Jumping ship from C++

Replies are listed 'Best First'.
Re^2: Jumping ship from C++ by morelenmir (Beadle) on Feb 02, 2014 at 16:48 UTC
Absolutely fascinating post!!! Not least because as part of my move away from C++ I have determined to be at least proficient in all the popular interpreted languages such as perl (obviously), python and ruby. The problem is after becoming at least comfortable in perl, whenever I try to give python a try I end up asking myself 'why bother?'. I run smack in to that wall of utterly rigid programming paradigm you mention and bounce clean off. Not to deride python too much of course. In some ways that kind of absolute pattern is good and helpful - and in the right mood I would even support it. I only wish C++ was a harshly defined as it would solve a lot of problems - accessor/mutator functions inside the same class hierarchy OR direct access to protected inherited data members and so on. However... perl is just so... seductive. I really think I can do absolutely ANYTHING I could ever want to do at the command line in perl, faster, clearer and enjoy doing it more too dammit! Currently I do draw the line at the console though. I do not think I would try a GUI app in perl and default back there to C++. But even that may come in time. "Aure Entuluva!" - Hurin Thalion at the Nirnaeth Arnoediad.	[reply]

Replies are listed 'Best First'.

Re^2: Jumping ship from C++
by morelenmir (Beadle) on Feb 02, 2014 at 16:48 UTC

Absolutely fascinating post!!! Not least because as part of my move away from C++ I have determined to be at least proficient in all the popular interpreted languages such as perl (obviously), python and ruby. The problem is after becoming at least comfortable in perl, whenever I try to give python a try I end up asking myself 'why bother?'. I run smack in to that wall of utterly rigid programming paradigm you mention and bounce clean off.

Not to deride python too much of course. In some ways that kind of absolute pattern is good and helpful - and in the right mood I would even support it. I only wish C++ was a harshly defined as it would solve a lot of problems - accessor/mutator functions inside the same class hierarchy OR direct access to protected inherited data members and so on. However... perl is just so... seductive. I really think I can do absolutely ANYTHING I could ever want to do at the command line in perl, faster, clearer and enjoy doing it more too dammit!

Currently I do draw the line at the console though. I do not think I would try a GUI app in perl and default back there to C++. But even that may come in time.

"Aure Entuluva!" - Hurin Thalion at the Nirnaeth Arnoediad.

[reply]