![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a question that has been bothering me for a while. WHY are goto top and goto bottom not Rushmore-optimisable, yet locate is? ISTM that it would have been easy enough to do. Sincerely, Gene Wirchenko Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices. |
#3
| |||
| |||
|
|
Goto top and goto bottom have no optimizable features.... |
#4
| |||
| |||
|
|
Josh Assing <xjoshx (AT) jassing (DOT) com> wrote: Goto top and goto bottom have no optimizable features.... Why would a plain locate be optimisable then? Depending on whether the index is ascending or descending, locate is logicaly equivalent to goto top or goto bottom It is this discrepancy that has me wondering. [snipped previous] Sincerely, Gene Wirchenko Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices. |
#5
| |||
| |||
|
|
I have a question that has been bothering me for a while. WHY are goto top and goto bottom not Rushmore-optimisable, yet locate is? ISTM that it would have been easy enough to do. Sincerely, Gene Wirchenko Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices. |
#6
| |||
| |||
|
|
LOCATE is scoped. GOTO isn't. |
#7
| |||
| |||
|
|
"Dan Freeman" <spam (AT) microsoft (DOT) com> wrote: LOCATE is scoped. GOTO isn't. locate and goto top are doing the exact same thing: finding the first record. [snip] Sincerely, Gene Wirchenko Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices. While they are getting to the same ent result they are doing it |
#8
| |||
| |||
|
|
"Dan Freeman" <spam (AT) microsoft (DOT) com> wrote: LOCATE is scoped. GOTO isn't. locate and goto top are doing the exact same thing: finding the first record. |
![]() |
| Thread Tools | |
| Display Modes | |
| |