11-04-2016, 11:25 PM
(11-04-2016, 10:25 PM)krzys_h Wrote: We are currently mostly using a custom linter made by @piotrdz - https://github.com/colobot/colobot-lint, but I don't think it has rules like the one you mentioned. It's usefulness is currently a bit limited anyway as it emits an awful amount of warnings related to old parts of original Colobot code, which in some places is horribly wrong like @tomaszkax86 mentioned.
The exact line you mention is a part of lights debugging code which is not really used so nobody noticed this error, it does appear to be wrong though.
openGLs 1.4, 2 and 3 all have that same lint err at the same exact place.
The colobot code doesn't seem bad at all in general, it is mostly good code and it works.
"cpplint" from the debian packages is good. It gives a lot of good answers without a lot of false positives and does identify bounds issues on arrays, which is the scariest stuff.
"geany" is a nice IDE editor that allows make and lint right on the panel so it is convenient.
The GoTo that I am working on is fairly complex ( very fast ) and comes from my actual robots.
A long explanation will be posted on my server( with pictures and charts) about how it works and where it might be integrated.
How do I communicate more effectively?
I appreciate what you all have done and I know it is a lot of work. It is a good framework and the concept of teaching programming in the game goals is a good thing to help people get started with programming.