Another thing that is really helpful, especially later when trying to understand or debug the code you wrote, it is put a prologue in each include and with each procedure that defines the purpose of the procedures, its input and output variables and what the include is doing. Good old text is a lot easier to read than code.
Use self defining variables rather than cryptic ones. When you look at a variable you should know immediately what it is used for.
Also use many comments, every line is good. This is especially important if your variables are not self defining. You may know what the code is doing when you write it but six months from now is is different story.
Barry
__._,_.___
Posted by: razzbarry@imageview.us
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (13) |
**** IMPORTANT PLEASE READ ****
This group is for the discussion between users only.
This is *NOT* technical support channel.
TO GET TECHNICAL SUPPORT send an e-mail directly to
SUPPORT {at} amibroker.com
TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
http://www.amibroker.com/feedback/
(submissions sent via other channels won't be considered)
For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/
This group is for the discussion between users only.
This is *NOT* technical support channel.
TO GET TECHNICAL SUPPORT send an e-mail directly to
SUPPORT {at} amibroker.com
TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
http://www.amibroker.com/feedback/
(submissions sent via other channels won't be considered)
For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/
.
__,_._,___
EmoticonEmoticon