No coder on this forum has earned my respect more than you Sr. Braga. Obrigado.
this is the sex man XD devs should commit this when its been fully tested... then someone could use it for a code editor program easily. Mock join devs as lua side polisher!!! haha
it's fully tested on 0.3.6. The tfs 0.4 is a sh~ and i am not working with it
it's fully tested on 0.3.6. The tfs 0.4 is a sh~ and i am not working with it
it's fully tested on 0.3.6. The tfs 0.4 is a sh~ and i am not working with it
Actually 0.4 has way more possibilities than 0.3.6.
At the same, many more crash holes, bugs etc. ^^
At the same, many more crash holes, bugs etc. ^^
About 1-2 hours to fix them all, I rather spend my time fixing them and then have more features than use outdated engine.
@Teh Maverick
Agree.
You don't even know, how much bugs 0.4 has. I don't think so, you'll spend 1-2 hours on fix them until you really know where is the bug, so all you can do is reading core dumps and fixing - but thats not just 1-2 hours.
You don't even know, how much bugs 0.4 has. I don't think so, you'll spend 1-2 hours on fix them until you really know where is the bug, so all you can do is reading core dumps and fixing - but thats not just 1-2 hours.
no tabs in code? notythis is the sex man XD devs should commit this when its been fully tested... then someone could use it for a code editor program easily. Mock join devs as lua side polisher!!! haha
Programs don't predict every situation or outcome. 5 hours to test every single class / variables / consts from every angle is not possible, having to run the tests would take a lot longer than 5 hours.
for example I managed to crash the textlogger.cpp class the other day. Would not have predicted that, due to the fact that it's the motherf**king text logger that I don't think has been changed in a while lol.
no tabs in code? noty