Porting to C++
-
- Trained
- Posts: 47
- Joined: 17 Jan 2010, 12:54
Porting to C++
I was just browsing the source, and I see some bits of C++ here and there, while the old code is still in C. Wanted to ask, are there any plans on gradually porting this piece by piece to the more user-friendly alternative, or it's gonna stay as it is forever? I was planning to mod the game but it's like... spaghetti.
Last edited by Zarel on 15 Mar 2010, 09:25, edited 1 time in total.
Reason: Renamed topic to something less vague
Reason: Renamed topic to something less vague
Re: A question.
Hey! That's very readable C code, I'll have you know. Seriously, if I can understand it, anyone can!
Re: A question.
Mods change the data files and graphics, not the source code.
-
- Trained
- Posts: 47
- Joined: 17 Jan 2010, 12:54
Re: A question.
I know, but stuff like camera behavior - even Pumpkin guys wrote in the comments it's very tangled.
Quite organized for C, but still unreadable to a foreigner.
Quite organized for C, but still unreadable to a foreigner.
Re: A question.
Unfortunately... C and C++ are the most efficient languages for games to be programmed in. Not very likely that anyone would want to port it to say visual basic.. because vb sux :p
Re: A question.
If you try to convert this code step by step to c++ you will be much faster to create just a new engine and build some interfaces to get the "old" grafics/sounds/ai scripts/etc. running on the new engine. But feel free to convert some parts and see for yourself what will happen to your time
Re: A question.
they appear to be adding more and more c++ code every time I look.Seismo wrote:If you try to convert this code step by step to c++ you will be much faster to create just a new engine and build some interfaces to get the "old" grafics/sounds/ai scripts/etc. running on the new engine. But feel free to convert some parts and see for yourself what will happen to your time
Re: A question.
Well, only the easier parts are converted. The common parts will be still left in spaghetti manner. I guess no one will ever change it due to extreme changes between branches/releases or similar nonsense reasons. I give up here to interest and waste my time for this project since i saw which "experts" working on this code. Windows hater programming on Wine under Linux software for Windows - well, anything else i should explain?
Re: A question.
Hey! No one here uses Wine at all. Why would you need Wine to code software for Windows?Seismo wrote:I give up here to interest and waste my time for this project since i saw which "experts" working on this code. Windows hater programming on Wine under Linux software for Windows - well, anything else i should explain?
fyi, I use my Windows machine whenever I do Warzone balancing (Excel for Mac doesn't support CSV very well at all). i-NoD and Buginator also code primarily on Windows. I also do plenty of testing on Windows.
None of the developers here hate Windows, some of us just prefer other operating systems more.
And none of us consider ourselves "experts" - that's a term that should really only be bestowed by a third party.
So yes, there's plenty you need to to explain, considering the fact that we make software for Windows was literally the only true fact in your entire post.
Re: A question.
May you are the exception of the rule, but every time i tried here to get rid of stupid issues i got things explaind with qt, linux, branch crap and other nonsense i never need to talk about. I am disappointed of some guys of your development team due to there absolut ignorance and incompetence and no one is kick them or even setting things correct. I just should not answer here, bacause of the fact that it will not change anything, but when i said a, so i should also say b. The part about spaghetti code is fully true and there are a lot of passages of this code needs to refact complete. But hey, hackers hacking hacked code, thats not software development. You will find better words for this...
Re: A question.
...I'm afraid I don't understand your English. Can you speak in your native language?Seismo wrote:May you are the exception of the rule, but every time i tried here to get rid of stupid issues i got things explaind with qt, linux, branch crap and other nonsense i never need to talk about. I am disappointed of some guys of your development team due to there absolut ignorance and incompetence and no one is kick them or even setting things correct. I just should not answer here, bacause of the fact that it will not change anything, but when i said a, so i should also say b. The part about spaghetti code is fully true and there are a lot of passages of this code needs to refact complete. But hey, hackers hacking hacked code, thats not software development. You will find better words for this...
I'll try to guess at what you're trying to say:
- What issues are you talking about? I asked Buginator, and he says we've committed several of your patches.
- What sort of ignorance are you encountering?
Things about Qt, Linux, and branching are important. We are not going to commit a patch if it happens to break compatibility with Linux or something...
Re: A question.
Crappy code is what professional programmers should be able to digest for breakfast.
Don't you know that most people who program aren't that good in structuring their code?
(in other words: get used to dealing with it, and it will benefit you even in your career... I know I did)
Don't you know that most people who program aren't that good in structuring their code?
(in other words: get used to dealing with it, and it will benefit you even in your career... I know I did)
Re: A question.
bornemix wrote:Crappy code is what professional programmers should be able to digest for breakfast.
Don't you know that most people who program aren't that good in structuring their code?
(in other words: get used to dealing with it, and it will benefit you even in your career... I know I did)
I'm good at structuring my code I'll have you know! xD
Re: A question.
That's not my point.
My point is that a good programmer should be able to read bad code without complaining.
My point is that a good programmer should be able to read bad code without complaining.
Re: A question.
I take it you don't do any programming then from your obvious ignorance shown here xDbornemix wrote:That's not my point.
My point is that a good programmer should be able to read bad code without complaining.
It's still got to be readable. Being a good programmer does not mean you can understand spaghetti straight away.