for example, if we use an indicator, we don't want it to predefine to use close. Even some part of an indicator can be different from what we know, like Amibroker SAR has default maximum cannot excess over 1. That may be logically make sense but how about if I want to test over 1? There are much more when we go inside every step to see what have been pre define.
another example is I don't want to use just open,close,high,low, I want to use any possible price within that day bar, and once the price trigger then do something, that is a block of coding in amibroker already, not much different from writing my who program.
just these two simple examples above, basically require a block of codes no matter amibroker or making my own program, but it is much harder to find out how to write every line in amibroker language, but very easy to know how to do that in programming, so parts like this actally saving a lot of time with real programming and these are what amibroker predine to stop me get correct backtest result and backtest what I really want to do, not backtest what is pre defined which is not what I want to backtest or use,.
》》》
so parts like this actally saving a lot of time with real programming and these are what amibroker predine to stop me get correct backtest result and backtest what I really want to do, not backtest what is pre defined which is not what I want to backtest or use,.
》》》
crunchor 發表於 13-9-6 14:07
there is no way calling amibroker AFL a real programming language, it is a "easy language".
It's AN easy language doesn't mean programming with it is not real programming. As a matter of fact, I found good AFL codes are much more elegant than primitive languages such as C# and JAVA, and that is what I called real programming.
[複製鏈接]
發表於 13-9-6 10:33
顯身卡
樓主
發表於 13-9-6 10:47