Tick Tock Tick Tock....

Timer100?

from WinCustomize Forums
Ok, I don't know if anyone has realised this or not but... The DesktopX Guide by Stardock displays Timers with 3 digits at the end as identifiers.. So everyone sets Timers as Timer100, Timer200 etc etc.. Me? Nope I've used Timer1, Timer2, Timer3, etc etc and I've had no problems. So less typing for you. Just something to bring to your attention if you hadn't realised already.
desktopx
8,210 views 8 replies
Reply #1 from WinCustomize Forums Top


Simple naming conventions. If you're running more than ten timers then it may be an issue.
Reply #2 from WinCustomize Forums Top
I can't imagine a scenario that would involve 10 timers for a single object hehe.. I might do that just to see what happened....
The Political Machine 2024
Reply #3 from WinCustomize Forums Top
I used to do the 100, 200, 300 thing. Until I realized that not everything in the example scripts have to be used 'as is'. Every now and then I might use Timer123, though. 
Reply #4 from WinCustomize Forums Top
I have been a programmer for over 25years and the 100, 200, 300 convention is as old as subroutines!
And I've had many occasions where it wasn't enough, in fact, we started using 1000,2000,3000 back in the '80s.
Course nowadays most languages allow proper names for subs with colons on the end...
Reply #5 from WinCustomize Forums Top
You, Garibaldi, have been programming longer than I've lived! (hehe How old must you feel now..) How old are Sub rountines? 30 years?
Reply #6 from WinCustomize Forums Top
we started using 1000,2000,3000 back in the '80s.
Course nowadays most languages allow proper names for subs with colons on the end


I do not remember Machine code, Assembler, FORTRAN, Cobol or LISP using or allowing any numbered lines, I though those came about with spaghetti coded Basic.
Reply #7 from WinCustomize Forums Top
Thanks Cyberium - I feel truly ancient now !
drej16 - I've never used a language with numbered lines (except Sinclair ZX BASIC!) but numeric labels used to be de rigeur even in some Assemblers (BLZ 100), RPL (G100) and even in things like JCL.
Never used COBOL, FORTRAN or LISP but from what I hear I had a lucky escape!
Even the early BASICs I used insisted on numeric labels, though.
Reply #8 from WinCustomize Forums Top
Garibaldi99 You are truely lucky to have missed COBOL, FORTRAN and LISP, they can be a real nightmare. Especially when debugging but hey at least I missed punchcards!