richmond62 wrote: ↑Sat Jan 13, 2024 1:48 pm
If you want to "pick a fight with me", be my guest, but pick a fight about something less trivial and worth fighting about.
I have
exactly zero interest in 'picking a fight with you' as it's not possible to ascribe a
negative number to this.
On the other hand, filling a page with weird code does bother me, especially it doesn't actually address the question asked.
But since you raise this as the issue, instead of the solution provided (your code does not actually do what he OP wanted):
It might be better to be more
explicit and less '
clever' when sharing code.
It's like 0.5 seconds more effort to write
tSeconds instead of
SEX, and the former is much clearer in what it means.
Naming conventions
DO matter. If you write a book
only you will ever read you can use any jumbled scrawls you like as long as you understand them. If the intention is for
others to read as well, you
have to use the commonly agreed alphabet, syntax and grammar, or there will be confusion.
LiveCode recommends a naming convention in the User Guide. I use the naming convention published by Richard here
https://fourthworld.com/embassy/article ... style.html:
Code: Select all
Char Meaning Example
g Global variable gMyGlobal
t Local variable tMyVar
s Script-local var sMyVar
p Parameter pMyParam
k Constant* kMyNumber
u custom prop uMyProp
I doubt the importance of naming conventions can be overstated...
Should I even bother mentioning the recommended capitalisation? (hint: search LiveCode's User Guide for 'camelCase')