Quote: "My project is getting bigger everyday, now it's almost 35k lines of code"
It'd be beneficial if you could post some excerpts (not the whole thing) of your program. Perhaps others can suggest alternative structures to further reduce down the programs foot print. The Dbpro compiler is known to be slow, which I suspect a by product of it's parsers internal string handling. So apart from throwing more and more cpu power at it, the only way to increase build time is give it less code to deal with up front.
What somebody out there should think of doing is writing a simple pre-processing tool that applies #constants, script comments through to Rename functions and other do-dads, from the input code up front. The resulting source is passed through to DBpro.
EDIT:
I've tested this before (years ago), but couldn't find the original examples, so these will have to do.
The following mock up code is create by a program, there\'s two versions of it. The human written version and a simulation of what a pre processor could do with it. Namely stripping comments, removing null lines & tabs and replacing long variable names with shorter one. Which is where I think the core problem with speed is, it\'s doing string compares when searching for variables, so the bigger the strings and or larger the keyword list becomes, more performance degrades.
The free Dbpro builds in the 11K lines version in about 80 seconds consistently, where the 3K line version builds in 55 seconds. Not earth shattering, but food for thought. (Test system
10 year old AlthonFX 3000. Attempting to build 30K lines took over 5 minutes, where i ended up stopping the process.
Sample code attached...
