PureBasic Forums - English

What difference does compiler speed make anyway? Especially when we're talking fractions of a second!

Karbon wrote:What difference does compiler speed make anyway? Especially when we're talking fractions of a second!

hmm... on that condition.... fractions of a second?



*SCNRA*

Speed and size is everything ... from programming to relationships Mind you, there are different parameters between the two ....

On a serious note ..

Take a look at the following ....

http://www.developerdotstar.com/community/node/479

.... and tell me the difference in compiler speed

I bet if they were using PureBasic, the compiling time may be smaller ...

netmaestro wrote:No, but I have VistaClock running sticky. That speeds up processing time for all applications by 300%

In the good old days the compile process was time for reflection. You could make a cup of coffee, think about your code, consider your approaches. Some of the best ideas came then, when the mind was still fresh from the challenge, but had gone into neutral, allowing free association, allowing the sub-conscious to have a say.

This obsession with fast compilation is counter-productive!

A fast compiler moves the dammits closer to the didthatfixits. That's the basic advantage.

PB does start to slow down on larger projects.

If there was an ability to work with Modules, which could be frozen as UserLibraries when working on a larger codebase, then that would solve the problem.

Then only the Module you are working on would need to be recompiled, making things run faster.

With v4, you should also keep in mind that having many predefined Macros will slowdown
the compilation a lot as well.
That is because every parsed token in the source must be checked against the macro table.

Just a hint to those building a set of predefined macros. Don't put too much
of them in your residents... you'll pay for it in compilation time

Dare2 wrote:

netmaestro wrote:No, but I have VistaClock running sticky. That speeds up processing time for all applications by 300%

In the good old days the compile process was time for reflection. You could make a cup of coffee, think about your code, consider your approaches. Some of the best ideas came then, when the mind was still fresh from the challenge, but had gone into neutral, allowing free association, allowing the sub-conscious to have a say.

This obsession with fast compilation is counter-productive!

So true!
I remember compiling an order-entry app on an IBM system/36 : took a whole day! We needed to work on different app's in the same time AND we had to be very attentive. Now it's more like : Trial and error.

I guess it's like everything else: every good side has a downside, the faster things go, the more my brain seems to be down.