
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
The requirement for naming classes is justified as long as the error in compiling the following is not eliminated
Indeed, there is not even a warping.
The class naming requirement is justified until the compilation error of the following is resolved
'Rect' - invalid cast operation WndContainer.mqh 386 25
'Rect' - parameter passed as reference, variable expected WndContainer.mqh 386 25
I understood from the ServiceDesk's reply that there are no plans to fix such errors. You cannot call a Rect class just because someone might have a Rect() method
Thanks for the info! I've never come across it, because I make all custom types (classes, structures and function pointers) with capital letters only. Such a terrible style I have.
The class naming requirement is justified until the compilation error of the following is resolved
'Rect' - invalid cast operation WndContainer.mqh 386 25
'Rect' - parameter passed as reference, variable expected WndContainer.mqh 386 25
I understood from the ServiceDesk's reply that there are no plans to fix such errors. You cannot call a Rect class just because someone might have a Rect() method
Thanks for the info! I've never come across it, because I make all custom types (classes, structures and function pointers) with capital letters only. Such a terrible style I have.
But what about defines? ))
What about the defines? ))
#undef
brutally )