- Question sur la fonction native Mql5 "OnChartEvent"
- Discussion of article "How to detect trends and chart patterns using MQL5"
- Closing orders at the cross of the MA does not work // Fermeture des ordres au croisement des MA ne fonctionne pas
I've applied automatic translation to your post. On the English forum, please write in English.
"as" is indeed highlighted in MetaEditor, but is not mentioned in the documentation or in the MetaTrader 5 release notes.
Here's what I found in the release notes from October 26, 2018:
https://www.metaquotes.net/en/metatrader5/news/5131
Added support for the inline, __inline and __forceinline specifiers when parsing code. The presence of the specifiers in the code causes no errors and does not affect the compilation. At the moment, this feature simplifies transferring С++ code to MQL5.
Perhaps "as" was added for some similar reason.
Furthermore, eight months ago, MetaQuotes' CEO announced that
"as" may have been added in preparation for this. But we can only guess.
and whether it is safe to use as a variable name
In my personal opinion, this is a bad idea.
There is no “as” keyword. Without code, we can only guess.
Yes there is an 'as' keyword. It's used with resource.
#resource "Python/model.onnx" as uchar ExtModel[]
- www.mql5.com
"as" is indeed highlighted in MetaEditor, but is not mentioned in the documentation or in the MetaTrader 5 release notes.
Here's what I found in the release notes from October 26, 2018:
Perhaps "as" was added for some similar reason.
Furthermore, eight months ago, MetaQuotes' CEO announced that
"as" may have been added in preparation for this. But we can only guess.
In my personal opinion, this is a bad idea.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use