Hey,

How do you handle the enormous compiling times of Lite-C (with big projects - code size above 512 KB)? Or better said: Do you also have the problem that the starting of your code (in unpublished mode) needs more than 2 minutes, while the same code needed just 3-4 (!!!) seconds in WDL (also with the latest beta)?

I'm generally a step-by-step programmer and must therefore check my code (by starting the engine) very very often, but this seems just to be impossible if I have more than 1 minute waiting-time EVERY start (and at the end see a syntax error). And this happens on a very good computer (3GB RAM, 4200+ CPU). I'm asking myself, how the situation is on other worse systems.

Recently Lukas wrote in the Beta-Forum:
Quote:


40 seconds for 1MB Code? You're lucky! My 526KB code needs 20 minutes!

One Programming hour:
1. Small changes in my script.
2. Compiling for 20 minutes
3. Being happy because of a syntax error because of a typo
4. correcting typo
5. compiling again...
6. Having a party because it doesn't work correctly
7. correcting script
8. Compliling again
9. It works... after one hour!

And this is how I have to make 3D-Tetris 2




Actually it is the very same for me..
10 minutes of checking a from wdl to lite-c converted code for errors
  • Wait 40 seconds for compiling => syntax error
  • Wait 40 seconds for compiling => see very very easy to fix error
  • Fix in 10 second
  • Wait 40 seconds for compiling => see difficult to fix error
  • Code the first try to fix the bug: 1 minute
  • Wait 40 seconds for compiling => bug is worse than before
  • Code the second try to fix the bug: another minute
  • Wait 40 seconds for compiling => works, but still a small bug
  • fix small bug in 20 seconds
  • Wait 40 seconds for compiling


=> 240 seconds waiting for compiling, 150 seconds for coding.. Is this workflow? no.. The result is a complete demotivation.. (how worse must be the situation for lukas whose code needs 20 minutes to compile - which is not a joke by the way).

Does this mean that you can not use Lite-C with big projects?
How do you programm efficiently with big projects (>512 KB) in Lite-C?
What do you do while the computer is compiling? Drinking coffee?

Could everybody who realized a big project with lite-c please comment how to get an acceptable workflow also with big code sizes?

thanks for answers,
Timo Stark

PS: This should not be a protest post against lite-C. Lite-C is needed and a good programming language. But in my opinion it is not useable in big projects in its current state.