I don't see how the compiler fits in this, as it's only used during creation and not execution (vs interpreter who is invoked at run-time).
I've seen an article about it, but was more about what to place in a loop and what not to or where to use vars/constants or calculations and if I remember correctly it concluded that unless you've done some serious design flaws or use extensively loops you won't get a much faster program by following these instructions.
What is your program supposed to do? Where are you facing delays?
adam_k
Practically a Posting Shark
803 posts since Jun 2011
Reputation Points: 256
Solved Threads: 149
Just a comment: Who said that pros write fast performing code? Nowadays most programmers don't really care about resources and execution time. In fact it's been a while since I've come across a programmer that took into account stuff like that or how to facilitate the user/ respect the flow of the process, etc.
On your programms keep it simple, well commented and recycle code whenever possible.
adam_k
Practically a Posting Shark
803 posts since Jun 2011
Reputation Points: 256
Solved Threads: 149
If I remember correctly it is slower to run:
for i= 1 to datagrid1.rows.count -1 'or whatever count that is
than
dim row_count as int
row_count = datagrid1.rows.count
for i=1 to row_count
The explanation is that in the first syntax the number of rows has to be calculated in every loop, while in the second it doesn't.
adam_k
Practically a Posting Shark
803 posts since Jun 2011
Reputation Points: 256
Solved Threads: 149