Errors, bugs, questions - page 2894

 
fxsaber:

In this picture the top Terminal is one chart per 5000 M1 bars.

Lower terminal - 20 charts, 10 Expert Advisors, CopyTicks on every tick, etc.


Because of such nonsense with upper Terminal, it's easy to get stuck with ArrayResize.

Have you forgotten what you were doing on the first terminal before you left one chart?

I think so.

Terminal doesn't need to get rid of previously raised caches quickly. It's waiting for the banquet to continue.
 

Renat Fatkhullin:
Вы забыли, что делали на первом терминале до того, как оставили один график?

I haven't forgotten.
There is no reason for the terminal to quickly get rid of the previously raised caches. It is waiting for the banquet to continue.

I know there won't be one. But the terminal doesn't care about that. You want 20 characters, put in NGB of memory. You want 200, 10N. 1000 - 50N. This is the banquet policy you see as correct.

 

Would you be kind enough to state the actual test conditions in each statement, without any "you should guess the load from comment N".

By your [un]oblivious statements you have completely disabled the credibility of your words.

 
Renat Fatkhullin:

Would you be kind enough to state the actual test conditions in each statement, without any "you should guess the load from comment N".

By your [un]oblivious statements you have completely disabled the credibility of your words.

Please pay attention to the posts here and in the English part, the profiler is not working, several builds already, just hangs the meta-editor.

 
Renat Fatkhullin:

Would you be kind enough to state the actual test conditions in each statement, without any "you should guess the load from comment N".

By your [un]oblivious statements you have completely disabled the credibility of your words.

Created a branch and there everything is constructive initially. Asked about Win10 in this thread.

 

Braking, has it always been like this?

// int f();

int Num = f(); // 'f' - undeclared identifier

int f() { return(0); }
 
fxsaber:

Has it always been like this?

yes

only withint f() forward;

but if this code is wrapped into a class, then the order of methods will not matter, even initialization of fields in the constructor should work

class A
{
   const int Num;
   int f(){return(0);}
public:
   A(): Num(f()) {}
};
 
fxsaber:

Braking, has it always been like this?

There is a bit of a contradiction here, because

void OnStart()
{
int Num = f(); //нормально
}
int f() { return(0); }

What is thedifference in principle?

 
Compilation error:
typedef void (*fn)();
void f() {}
fn g() { return f; }
oid OnStart()
{
        g()(); //Error: ')' - expression expected
}
 
Igor Makanu:

only with a forward-descriptive int f();

Thank you.

Reason: