Alex, btw, thanks for the linky to Ruby, I was going to learn it, but I forgot to get around to it. It's not bad, the method creation system is fairly straight forward. I think the debate over {} or not is silly, what matters is two things. 1) How many systems adopt the use of said language and 2) how well the compilers are built. If 1 is all a language has going for it and 2 is shit, then it's logical to try another language. As for why C++ is used more than say Java or Python, that's simple, louder voices usually get heard more than the more quieter kind. Essentially, Python was built by programmers for programmers, the same it seems with Ruby and etc, where it's really not needed to put effort in getting the word out, it gets out simply because of the normal shop talk. That's why you see so many books now devoted to Python [I don't know if there's any books published on Ruby, maybe you can give us a, FTL'd Amazon linky for that.
] just because of that chatter.
I think C++ is decent, the only complaint I have is the mixture of C like syntax and un-C like syntax, so it confuses a user of C on what the fuck they're doing, like the operator overloading. I'm still going WTF about the syntax there. Usually I ask a wouldbe programmer what they want to do. If they say games. I point toward C, possibly C++ if the given game requires it, but I usually say stick with the old fart language only because there's loads of libraries and documents on how to do shit with it. Plus, most games don't really need OOP to do most of their work. I dare say procedural programming is better suited for games in that it makes the general game leaner because you have to think in steps before you do a part of the game you want to do [like how do I handle calls for the 3d sound library...].
Sorry for the lecture, but that's what I've been thinking about all day.
-- Bridget
P.S. I love Pure BASIC too, so there!
The Free Talk Live BBS
Poll
10 (37%)
Author
Topic: Text editor (Read 8752 times)