Errors, bugs, questions - page 2212
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
Dear developers, please clarify, is it normal that the compiler does not give a warning about type conversion in such a string?
If here
(*) implies A::a = 2, not ::a = 2
then S::q = S::z should be implied there too, not S::q = ::z
Why would S::z be implied there, if the expression is not in a function of the S object, but at the global level.
The global level is, that is, ::z is implied - without any of these.
Dear developers, please clarify, is it normal that the compiler does not give a warning about type conversion in such a string?
Strange... It doesn't say anything to me...
That's strange... Mine doesn't say anything...
That's just it, he doesn't write anything. And he should, I think...
That's just it, he doesn't write anything. But it should, I think...
You mean the result of int is converted to bool ?
Yes, in theory, it should generate a warning.
You mean the result of int is converted to bool ?
Yes, it's supposed to give a warning.
Yes, the implicit conversion goes without a warning.
That's just it, he doesn't write anything. But he should, I think...
He should. I can guess why it doesn't. Zero is assumed to be false, anything not zero is true.
that is.
Probably by these rules they do, although again, I think warning should be
Write in the SD.
Write to the SD
Yes, I did... but no reply. In general, the BODs work strangely: I write an application, the application is accepted for consideration. And then silence. Why should I submit an application if I'm not going to answer it? And so on absolutely every application.
Dear developers, please clarify, is it normal that the compiler doesn't give a warning about type conversion in such a string?
Developers' answer:
You need to be more careful.
Dear developers, please clarify, is it normal that the compiler does not give a warning about type conversion in such a string?
Bars see what it returns and what you are trying to equate it to.