Errors, bugs, questions - page 2034

 
Is the execution of stops during a gap already fixed?
 
Vitaly Muzichenko:

Dig out the home button with a screwdriver :)


No, that's not the problem. As it happens both when MT5 is in the background and when even the chart is different.

 

I suppose the problem is because of this strange field:

 //---- profit calculation parameters
   int               unknown2;

It wasn't there in the original, where did it come from?


It is 4 bytes for address alignment in the structure.

previous gtc_pendings and subsequent contract_size field are read correctly

 

Please send me a link to the topic: . sl: 0.00000 tp: 0.00000 failed [Off quotes]

 

Compilation error

#define  MACRO1( X, Y )  X/**/##Y
#define  MACRO2( X, Y )  X##/**/ Y
void f5() {}
void OnStart()
{
        MACRO1( f, 5 )(); //нормально
        MACRO2( f, 5 )(); //error: 'f/' - undeclared identifier
}
 
A100:

Error during compilation

Would have banned MACRO1 as well.

 
fxsaber:

Would have banned MACRO1 as well.

Based on what? Just because you felt like it?

There is a general rule: comments can be in any part of the program. If you do not use comments, it does not mean that others do not

 
A100:

Based on what? Just because you feel like it?

There's a general rule: comments can be in any part of the program. Just because you don't use comments doesn't mean others don't

Because it's as twisted as this.

#define  MACRO(A,B)  A## \
                      B

void OnStart()
{
  int j2;
  int i = MACRO(j,2);
}


By the way, it looks like a bug.

#define  MACRO(A,B)  A##B

void OnStart()
{
  int i = MACRO(1,2); // '12' - undeclared identifier
}
 
fxsaber:

Because it's as twisted as this.

By the way, it looks like a bug.

No real argument - just say so. In your mind it can't be a bug because you can't write it that way - it's like replacing /**/ comments in the example above with spaces

#define  MACRO2( X, Y )  X## Y
 
A100:

If you don't have a solid argument, just say so. It can't be a bug in your mind

void OnStart()
{
  int j2;
  int i = j/**/2;
}

Why shouldn't a macro cause an error in this place? Just don't cite C++ as an argument, where someone thought for others.