Errors, bugs, questions - page 2864
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
So why doesn't it work?
Most likely, this approach doesn't work anywhere. Because there is a substitution going on where the VALUE on the right is undefined.
This approach probably doesn't work anywhere. As there is a substitution going on where the VALUE on the right is undefined.
Yes, and it is evil to change someone else's macro substitution.
Without this evil, it would not have happened.
And it's evil to change someone else's macro substitution. Especially if they are predefined environment macros. It doesn't matter where in the end, after all the files of the project are assembled, the overriding of the macro will end up. You'd better define your own _VALUE macro.
May I ask why you can't use a VALUE assignment to a global variable and multiply it and substitute it in the final define?
You can, but then the meaning of macro substitution is lost (substitute values in the code). All hope remains on the compiler, that it converts const type (have you, by the way, defined the variable type?) to c++ constexpr type
But otherwise, yes, you can.
But then, yes, you can.
It won't work with that.
It won't work with this one.
This approach probably doesn't work anywhere. As there is such a substitution going on, where the VALUE on the right is not defined.
Apparently, I don't understand how the compiler works at all. I imagined that strings are parsed sequentially. So there is no undefined value on the right:
Apparently, I don't understand how the compiler works at all. I imagined that strings are analysed sequentially. So there is no undefined value on the right:
Works top-down like text replacement. I.e. "TMP" will be replaced by "VALUE".
Apparently, I don't understand how the compiler works at all. I imagined that strings are analysed sequentially. So there is no undefined value on the right:
It's not the compiler - it's the preprocessor)
turns into
, and your VALUE is undefined.