Hi all,
I'm about to embark on a programming tutorial involving C. And...I was wondering...since I understand the concepts of OOP (Java)...should'nt I just learn C++ instead?
The software has to run on a Linux system and pretty dep down in the layers too...at the DE level, in fact...
So..C or C++?
Is (for example) XFCE written in C or in C++?
Thanks
Melissa

That's not deep? Some DEs use Python or JavaScript.

What do other people use for the desktop environment you're targetting?

If that's Xfce, check the relevant repositories.

If you don't have a reason to use a different language to everyone else, then do not.

1 members found this post helpful.

If you're thinking of writing Gnome/GTK apps (XFCE uses GTK), then C.
If you want to get all historic and investigate the native X11 libraries: libXaw, libXt, libX11/xcb, those are also C.

Ultimately, the choice will depend on what your end goal is. Besides, no reason not to learn both C and C++.

1 members found this post helpful.

Keep in mind that you'll likely be working with libraries that are written in C and meant to be used to be used in C.

A quick glance at GitHub says that Xfce4 is written in C.

If the tutorial is in C, then you should consider sticking with C. That is if I understand that point correctly, which is that you're going to follow a programming tutorial that already has been worked out? If so, then whatever language they use, you should continue with.

Yes, some DE's use C++, like Qt and FLTK, I guess GTK uses C, from seen above, I do not know.

But hey ... if you know Java, and more pointedly OOP, then I feel you know C++.

You can't go wrong by learning C, and C++ is a superset above it.

As to what XFCE is written in, I do not know.

No learning is wasted time, but let's note that C++ is still under intensive development, albeit it is already Huge (with capital H).

Hi, I'm an ignorant but for me the answer is: "both and much more"; c and c++ always on the desk, it and it's history it's philosophy and it's people push up you to the intellectual glory.

From the lambda calculus to the stars!

For your programs, I recommend writing largely in C style, but compiling with C++. This will let you selectively use the C++ features that improve upon C.

A C++ program can call C libraries as though nothing had changed.
Ed

Swap "or" with "and!"

"Should I learn C?" Yes. "Should I learn C++?" Yes. (And I'd go on to say: "Should I learn ____?" Yes. Languages are, after all, "the tools of your trade." Studying new languages is a bit of a "nerd hobby" for me.

The C language was designed to be "better than assembler." The original Unix operating system was mostly written in it, and that's why it was invented in the first place. (Of course, so was Linux.)

C++ was originally implemented as a preprocessor which emitted C source code. The language implements many useful object-oriented features, but by doing so it "steps away from assembler." This for example is why the Linux kernel is not written in it. But, if I needed to write a binary program today, C++ is most likely to be the trusty hammer that I'd reach for, and recommend.

So, go ahead and take that course in "C." Next, take a similar course in "C++."

istr that Linus has a low opinion of C++.

There are technical reasons (like ABI) to not write OS kernels in C++. They don’t apply if you’re writing desktop apps.

C++ programs, like most programs, are very dependent on a "runtime library" for their successful operation, and many of C++'s goodies are implemented using it. The language implementation also tacitly assumes that it is "running in userland."