Low Level Custom Backtest and MaxOpenPositions

[Milosz]

@Dionysos

It messes with my buy/sell + stops if I don't do it this way, also the trailing stops are visualized wrongly.

@Dionysos Your problem must be somewhere else, because (for the reasons explained by @mradtke), this part of your code is wrong:

for( i = 0; i < Max(Entryperiod,100); i++ )  
{Buy=Sell=Cover=Short=null;}	

You are not using subscript operators [] allowing to access/assign individual array elements, so it just repeats the same line (assigning all elements of each array with the value null) minimum 100 times. One such line is enough. Your two above lines equal:

Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
Buy=Sell=Cover=Short=null;
...etc.

I think that you agree, that repeating this line x times doesn't make much sense

When scalar becomes an array, aka. type coercion in AFL

Since the subject of data types surfaced in this thread: Send orders to IB on next bar (Intraday) Here are some comments regarding data types in AFL. While some users who familiarized a bit with array handling in AFL may think that everything is an array in AFL, that is not the case. The data type depends on value assigned to variable. If you assign scalar (number) the variable type will be scalar (floating point number, 4 bytes long). So if you assign a number to variable like this: var1 =…

Accessing array elements: [ ] - subscript operator:
www.amibroker.com/guide/a_language.html