Yes. And, you can deconstruct things further by having separate includes for entries, exits, money management, etc.
You pay a small price for using #include, but it allows you to write modular code to very quickly mix and match elements of a trading system. Stictly speaking, we should probably be using #include_once. The parameter based procedure approach is perhaps more comfortable for anyone coming from a formal programming language. It allows for better encapsulation. Though, in my sample I neglected to declare the variables used inside of the procedure as local. Using only local variables in any given procedure would secure against unintended interaction between modules. Mike --- In [email protected], "progster01" <progs...@...> wrote: > > Mike, > > Great suggestions! > > The general idea could be extended to the point that your final "runnable" > code files consist of nothing but includes, something like this: > > MyTest_01.afl > > #include <GlobalStuff_01.afl> > #include <System_01.afl> > #include <CustomBacktest_01.afl> >
