50g Mini-Challenge: Number of positive divisors of x!

[Joe Horn]

(10-02-2017 06:43 AM)Gerald H Wrote:  

(10-02-2017 05:30 AM)Joe Horn Wrote:  I keep << -40 CF MEM DROP 0.5 WAIT TEVAL -40 SF >> assigned to a key for accurate timings.

Why do you have MEM in the programme? TEVAL does garbage collection.

Wow, so it does! I never knew that. Good to know. I've removed MEM DROP from my assignment. Thank you!

(10-02-2017 06:43 AM)Gerald H Wrote:  What's the point of 0.5 WAIT?

Short answer: Because I got annoyed having to tap the assigned key very rapidly, to prevent TEVAL's result from being polluted by the system slowdown caused by the keydown event.

Longer answer: Including 0.5 WAIT is only useful if TEVAL is executed via a key assignment. Try assigning just TEVAL by itself to a key, and you'll notice that you'll get the longest timings if you press and hold down the key during the entire TEVAL, and the fastest timings if you very rapidly tap the key (releasing the key before TEVAL even has a chance to begin), and various timings in between (when the key is released after TEVAL starts but before it finishes). Since my goal was reliably similar timings, I include 0.5 WAIT in the key assignment, which gives plenty of time for the key to be released before TEVAL begins to actually begin timing.

-40 CF turns off the "ticking" clock display, which causes a system interrupt once every second, which messes up timings. -40 SF is included because having the ticking clock display is the only known workaround for the Busy Bug.