These are good questions, Roland, and indeed it would ideal if such
things were in hand right now.
But to create a comprehensive style guide for IDE contributions we'd
have another scope of work to address, in addition to other
opportunities at hand.
If someone wants to dive in and put
i and j are about as far as I go with nested repeats. Although sometimes I
further process the resulting tEmpList in yet another repeat loop. It
helps me to follow my own code if I can produce a list with modifications,
and put tEmpList (into msg) before proceeding with more processing.
Recently, Bernd Niggeman posted a stack that
displays LiveCode Dictionary content
in a different way.
Could Livecode Community Developers create a
"Wizard" plugin that check scripts and suggest
changes according to naming conventions?
Notice that already exists a plugin created by
The problem with ambiguous counter names is that often there are nested repeat
loops and knowing which counter for which loop is crucial to understanding the
code. I almost never use i, j, k, l and when I do, I usually regret the choice
and remember why I don't use them.
> On Apr 27,
I am referring to the note from Richard and to our discussion about
Contribution From The Community - expanding the developer base to "hundreds
and thousands of users" -- even if only 10 will remain?.
> At the bottom of the "Contributing" page for the LC code base there are