"Like the concept of best practice, defining what constitutes innovation
is probably a relative term and a moving target at best."
found at : http://strengthofweakties.org/?cat=11
and this is probably the truth. What constitutes 'canonical' programming is
surely a matter of taste, and I would ask the following question:
1. Who is going to look at the code apart from yourself?
If the answer is 'no one' then you really can please yourself.
If the answer is not 'no one' then it very much depends on who
that 'one' or 'ones' is going to be; and, to be honest, how much you
want them to understand your code.
Now, consistency is always a good thing; even for yourself - there is
nothing half as "fun" as looking at some code you wrote six months
ago and finding you have difficulty understanding it. :)
The other good idea is to pop comments in your code, such as:
--this is where the cycles of the FOR-NEXT "embedded 24" loop are counted
so that you don't get your "end if" s "in a twist".
---------------------------------------------------------------------------------------
One of the 'cyclical chestnuts' that comes up on this Use-List is about
the use of abbreviated forms in code (such as 'btn') and whether that
makes things murkier for other readers of code. The fact that it is a
cyclical chestnut should tell us that it is a moving target, and it all
depends on question 1.
Bill Andersen wrote:
Can someone point me to a "Best Practices" or good itermediate tutorial
on programming in Rev. I've been able to do quite a bit and can use
the dictionary to learn how to use the language, but I'm having trouble
understanding how most people use Globals, Custom Properties, etc.
I've read pro and cons on using globals. I've tried to write functions
and pass params around to avoid them (which I think is best), but then
there are times a global seems to be a better idea... OR would a Custom
Property be better? I just don't know how others would do it. I've
looked through a lot of examples and it seems it is all over the board!
I know it isn't written in stone (and really a personal preference),
but has someone put together a "Best Practices" document?
We really need a Rev for Dummies book!
Bill
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
