Thread: WxWidgets in C?

It's C++, because typically frameworks are C++, since frameworks benefit more from being written in C++, since software often benefit more from being written in C++.
In all seriousness, though, if you want to write computer software, you should really look into C++ someday. C just wasn't designed for today's requirements and needs in mind.

> C just wasn't designed for today's requirements and needs in mind.
Poppy cock. Define "today's requirements", because if you can do that -- then you can do what many companies have failed to do.

> It's C++, because typically frameworks are C++
No they're not. The mix is pretty even, if not slightly weighted towards the other.
I'd say writing the frameworks in C is far better than C++, because you don't exclude those who want to use C (nor do you exclude those who want to use C++). Or at least you don't have to write a binding.

It depends what you like, GUIs often work best when they're object oriented. However, many, many, many (x 10^99999) frameworks follow the procedural paradigm.

Originally Posted by zacs7

> C just wasn't designed for today's requirements and needs in mind.
Poppy cock.

You mean to say that that is untrue then?

> You mean to say that that is untrue then?
Yes.

C has a purpose. You don't go and use a screw driver for everthing and ignore the hammer, just because screws were invented do you?

Originally Posted by zacs7

> You mean to say that that is untrue then?
Yes.

Oh! That's very amusing.

C has a purpose. You don't go and use a screw driver for everthing and ignore the hammer, just because screws were invented do you?

I don't deny that. It has a purpose because no other alternative exists yet, but it isn't computer software.
C belongs to embedded systems. And that's where neither assembly nor C++ is used.
And frankly, C++ being close to the hardware too, embedded systems could really use C++ instead of C, but unfortunately, people today doesn't seem to acknowledge that (in a sense that they develop the systems for programming with C instead of C++).

Every language has its flaws. You don't think C# is free of defects, do you? There are plenty of people complaining on that language, too.
And a lot of these "flaws" can be circumvented. For example, use a vector and its .at function, and you avoid the "accessing the 7th element of a 5-element array."

C++ continues to evolve, too. Although there doesn't seem to be that many changes to the language itself (mostly additions to the standard library), there is progress being made. There was a time when smart pointers were unheard of. Now they're becoming all the more common and are being added to the standard library.

And it makes sense that C++ doesn't run in a managed environment. If it would, then it wouldn't be the successor of C, because it would break what made it an evolution of C--the proximity to the hardware and the raw speed of C.
There is C# if you like managed environments. Myself, I don't like the overhead.