Search Results
Searched for posts by zenith in all forums

Showing results 21 - 24 out of 24 total
Modify your search
Posted by zenith, Jun 27, 2015 at 4:11 pm
I agree with Pent and capristo. IMO there are already enough (if not too many) obscure messages in IVAN.

At least in UT those would be too confusing/superfluous for new players. On more advanced levels I think they're okay.
Posted by zenith, Jun 23, 2015 at 8:21 am
chaostrom, hah!

murlock wrote
Supporting DJGPP and C++11 at same time seems very difficult

Excellent point. If we're going to integrate C++11 then I think DJGPP is of less priority and should be dropped.
Posted by zenith, Jun 22, 2015 at 2:52 pm
No problem, glad to help!

Regarding the mixture of spaces and tabs in the code, and some slight variations on coding styles, etc.:

I think that, especially now that multiple people have started contributing to the project, we should establish a set of explicit rules, some kind of "IVAN coding standard / style guide", to help keep the codebase consistent and clean, as it was at the time of the original v0.50 release.


Regarding DJGPP, I agree that it clutters the graphics code a bit, but just last year I ran IVAN on my ancient computer with DOS (just for fun) and it actually worked. So I think it's a nice feature to have, and it would be a shame to just throw it away, even though nobody uses DOS on a daily basis. (Also it adds geek value.)
Posted by zenith, Jun 18, 2015 at 11:46 am
Inspired by murlock's SDL2 patch, a thought crossed my mind — Should we perhaps convert the project to C++11 as well?

I mean, IVAN currently uses C++98, which is already 17 years old. I think C++11 would be a great step forward.

Some of the C++11 features I'd love to have in the IVAN source code include smart pointers, override (and final), delegating constructors, range-based for, constexpr, auto, = delete, = default; maybe also: new algorithms in <algorithm>, decltype, lambdas, enum class, static_assert; to name a few.

This is of course a lot of work. I think it could be manageable in chunks, one feature at a time. And not necessarily all of the above. I'd be happy to do this. If anyone wants to help, that'd be awesome.

What do you think?