Ruby Question and Unity Test Framework feedback wanted.

[stahta01]

I have decide that I need to learn a Unit Testing Framework.

I have decided to try Unity; it is mentioned in Unit Testing in C: Tools and Conventions | Dr Dobb's

Unity site is Throw The Switch! - White Papers - Unity Intro

I party decided on Unity because it uses just "C" with no "C++" in the Unit Testing Framework; also, because it uses Ruby to do higher level work.

I have decided learning OOP using C++ has not really worked well for me. So, I wonder if Ruby is considered a good language to learn OOP?

I would also like any positive or negative feedback on using Unity Test Framework.

Tim S.

[whiteflags]

I have decided learning OOP using C++ has not really worked well for me. So, I wonder if Ruby is considered a good language to learn OOP?

I hope I don't sound like a jerk, but what would make a good language to learn OOP, for you? Ruby has some syntax differences, but it is still OOP, so OOP itself might be what's really confusing.

[SirPrattlepod]

Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the Universe is winning.

[stahta01]

I hope I don't sound like a jerk, but what would make a good language to learn OOP, for you? Ruby has some syntax differences, but it is still OOP, so OOP itself might be what's really confusing.

Thinking in OOP terms is the problem; I am hoping the cause is C++ is so much like C that it is causing me to still think like I do in C.

Tim S.

[Elkvis]

C++ is so much like C that it is causing me to still think like I do in C.

this is likely the root of your problem. it took me a long time to go from a purely procedural mindset to include object oriented programming, so I can relate to what you're going through.

the ideal goal for a programmer should not be to think in terms of only procedural, or only object oriented, or only functional programming, for a particular program, but rather to critically think about the problem you're trying to solve, and decide how aspects of each paradigm apply to your particular problem, and use some of each to address the various components of the program you're trying to write. with few exceptions, no problem is best solved by a single paradigm. this is what makes C++ so powerful. it embraces all programming paradigms, and allows you to mix them in a single program.

[vart]

causing me to still think like I do in C.

And why you are not thinking OOP when in C?
Language should not determine how you thinking.

Language determines how you implement what you have decided to do during your "thinking phase"

[phantomotap]

Thinking in OOP terms is the problem; I am hoping the cause is C++ is so much like C that it is causing me to still think like I do in C.

O_o

Well, thinking in "OOP" may be a part of your problem, but that, in my opinion, is not the root of your problem.

It seems to me that your problem with C++ is that you delved too deeply into C++ before you really built a foundation of solving problems the C++ way.

In so doing, I believe you found yourself overwhelmed with the C++ way and simply defaulted to the C way simply because you understood that approach.

If you repeat this fault, trying to move too quickly, you will have the same problem with Ruby or any other language: you will not have given yourself enough time to learn how express your thoughts well with such other languages so find yourself sticking with the C way.

I don't intend to offend at all. I hope you know this, but I've seen this before, and have also used you as an example for others.

I'd really recommend Python instead, but feel free to give Ruby a try.

In any event, if your willing to give C++ another go, step back all the way from what you know as a programmer. Start learning C++ as if you knew nothing about programming in general. Do all those crappy, simplistic, boring examples you could do using C with your eyes closed. Build a new foundation with C++ way with that approach and you'll be swimming.

Language determines how you implement what you have decided to do during your "thinking phase"

On the other hand, languages determines how you implement what you have decided to do during your "thinking phase".

Nope. I'm not making a silly joke. My point is, your thoughts about implementing solutions are necessarily bent by your experiences.

You may feel free to deny this all you like, but at the end of the day, it is a simple fact: our thought processes as programmers are shaped by the tools we use.

[Edit]
I'm not looking for an argument about "OOP" in C. I'm not interested. Yes, you can do "OOP" in C. You can do "OOP" in assembler, Javascript, and common LISP, but that doesn't make "OOP" constructs the right tool for the job in those languages.
[/Edit]

stahta01 has very likely avoid many aspects of "OOP" in C for the same reasons a C programmer generally avoids function constructs: the native support is atrocious so other techniques are often far more appropriate to the solution.

If stahta01 is extremely familiar with C constructs, as I feel comfortable assuming, his experience surely shapes his approach to solving problems with C++ thanks to the, false, familiarity.

Besides, a C approach to "OOP" constructs is generally flawed C++ out of the gate.

Soma

[whiteflags]

Speaking of -- kinda off topic -- you have no idea how many times I read your name as shasta.