...
best regards,
herman
Friday, August 1, 2008, 9:07:31 PM, you wrote:
> Hello veteran AFL programmers,
> I am still working on developing a consistent AFL style.
> I am writing a lot of AFL functions. I try to make as many things
> functions as I can so that I can reuse a lot of code. It also makes
> it easier for the editor to find syntax errors since my main code is
> indicator only and the syntax check pass does not see that code since
> it runs without the Chart ID.
> My trading platform is over 5000 lines of AFL (I keep adding more, and
> it keeps getting smaller...LOL). About half of that is functions. I
> pass a lot of data through global variables and arrays between
> functions for the state of the system. It was the only efficient way
> that I knew how to make code modular was to have the data common. AFL
> is largely based on that premise already with special state variables
> and price/trade arrays.
> Right now, I have a mix of variable initializations and just global
> declarations at the top of the formula so that I don't have to declare
> the globals in each function. I still have a lot of global
> declarations in some functions, but I want to finish getting rid of
> them and just have them declared at the top with a good description of
> how they are used.
> I had it in my head that a bunch of global declarations in a
> frequently called function would slow down the execution of the
> function. Am I right about that?
> I thought I could just mention the names of the input and output
> variables in the header comments if needed for documentation.
> I am also slowly changing my comments from // to /* */ so that they
> are not in the execution path.
> I am starting to make my variable names longer so that they are more
> descriptive of the data they hold.
> I have some naming conventions like FP_Name for variables that are
> part of my Flexible Parameters system and exist outside of that module.
> I am now planning on adding GP_Name for global parameter names and
> SP_Name for symbol specific parameter names. In Flexible Parameters,
> I give my parameters distinct names independent of their displayed
> labels. Those will be more than mere convention in that they will
> cause the parameters to be saved in a different file folder.
> What kind of naming conventions do you use that you are proud of?
> Any other unique features of your program style that you think are
> worth copying?
> Thanks for sharing your style ideas.
> Best regards,
> Dennis