This article will be very useful to Metatrader beginners interested in building their custom indicators or expert advisors. In this articles you can learn the MQL5 Syntax and Best Practices.
Understanding MQL5 Syntax Basics
Mastering MQL5 syntax and adhering to coding best practices is very important to create efficient Expert Advisors (EAs), indicators, and scripts in MetaTrader 5.
MQL5’s C++-inspired structure offers immense power for algorithmic trading, but clean, maintainable code is what turns potential into results.
In this article you will learn MQL5 syntax essentials, practical examples, and best practices, including naming conventions, case usage, indentation, and bracket placement, to help you excel in your trading projects.
MQL5 Syntax
MQL5 syntax is structured and precise.
You start with a keywork or operator or variables and constants.
You use brackets to group code together.
Lines are closed by a ;
Here’s a simple script to print the current Bid price:
|
1 2 3 4 5 6 7 |
//OnStart Functions void OnStart(){ //Declare BidPrice variable and assign current Bid value double BidPrice = SymbolInfoDouble(Symbol(),SYMBOL_BID); //Print the current bid price Print("Current Bid Price: ", BidPrice); } |
The OnStart() function runs on script execution, MarketInfo() fetches market data, and Print() logs it.
Note the semicolon (;) which is necessary. Variables require explicit types (double, int, etc.), like:
|
1 2 |
double tradeEntryPrice = 1.2345; int openOrders = 0; |
This strictness ensures performance, critical for real-time trading tools.
Some content is also available in the official documentation.
MQL5 Best Practices
Best practices are those “good to do” actions and styles that can make a difference between a very messy code and a clean and efficient one.
Best practices are not strictly required and are also not “set in stone” meaning you can make your own best practices that make sense for you.
Here are some common and useful MQL5 Best Practices.
Use Descriptive, Consistent Naming Conventions
Clear variable and function names are non-negotiable in MQL5 coding.
You can use camelCase for variables and functions, reserving PascalCase for classes (if using OOP).
I myself like to capitalize the first letter of each word in all variables.
Avoid vague names like x or temp unless it’s a very temporary variable.:
|
1 2 3 4 5 6 7 |
// Poor naming double x = 50.0; double y = iMA(NULL, 0, 20, 0, MODE_SMA, PRICE_CLOSE); // Better naming double stopLossDistance = 50.0; double movingAverageValue = iMA(NULL, 0, 20, 0, MODE_SMA, PRICE_CLOSE); |
Prefix constants with CONST_ (all caps) to distinguish them:
|
1 |
const double CONST_PIP_VALUE = 0.0001; |
This clarity saves debugging time and shines in MQL5 courses or tools on your site.
Leverage Case Usage for Readability
Stick to conventions: lowercase for keywords (if, for), camelCase or capitalizing variables/functions (calculateProfit), and UPPER_CASE for constants.
This visual hierarchy makes code scannable:
|
1 2 3 4 5 |
double calculateProfit(double entryPrice) { const double TARGET_PIPS = 20.0; return (Bid - entryPrice) / TARGET_PIPS; } |
Consistency here signals professionalism and expertise.
Indent Code for Structure
Proper indentation aligns your code logically.
Use 2 or 3 spaces (be consistent) to nest blocks within functions, loops, or conditionals:
|
1 2 3 4 5 6 7 8 9 10 11 12 |
void OnTick() { if(IsNewBar()) { double maFast = iMA(NULL, 0, 10, 0, MODE_EMA, PRICE_CLOSE); double maSlow = iMA(NULL, 0, 50, 0, MODE_EMA, PRICE_CLOSE); if(maFast > maSlow) { Print("Bullish crossover detected!"); } } } |
This layout makes nested logic easy to follow, reducing errors.
Place Brackets Deliberately
Brackets {} define code blocks, and their placement matters.
The “Egyptian” style (opening bracket on the same line) is compact and widely adopted in MQL5:
|
1 2 3 4 5 |
if(tradeIsActive) { Print("Trade is still open"); } else { Print("No active trades"); } |
Avoid single-line if statements without brackets — they’re error-prone:
|
1 2 3 4 5 6 7 |
// Risky if(condition) Print("Yes"); // Safer if(condition) { Print("Yes"); } |
Consistency in bracket style keeps your codebase polished.
Add Comments for Context
Extensive use of comments is very useful.
Document why with comments (// or /* */):
|
1 2 |
// Check if 20-pip profit target is hit double profitTarget = entryPrice + 20 * Point; |
A header block adds professionalism:
|
1 2 3 4 5 6 |
/* EA Name: TrendCatcher Purpose: Trades EMA crossovers Author: YourName Date: March 2025 */ |
Optimize with Functions
Use functions to make your code more modular.
Functions help keep your code clean and maintainable, and reduce the risk of repeated errors.
|
1 2 3 4 5 6 7 8 9 10 |
bool isProfitTargetHit(double entryPrice, double targetPips) { double currentPrice = Bid; return currentPrice >= entryPrice + targetPips * Point; } void OnTick() { if(isProfitTargetHit(1.2000, 20)) { Print("Profit target reached!"); } } |
Handle Errors Robustly
I need to highlight how important error handling is.
Expert Advisors often have full control on your funds, they trade for you, open and close trades, you need to trust that they are operating in the right way.
Errors and unexpected actions happen with any software, and it is paramount to be able to handle unexpected events should they happen.
Catch issues with GetLastError():
|
1 2 3 |
if(!OrderSend(Symbol(), OP_BUY, 0.1, Ask, 3, 0, 0, "MyEA", 0, 0, clrGreen)) { Print("Order failed with error #", GetLastError()); } |
Final Thoughts
Writing clean MQL5 code blends syntax mastery with disciplined habits.
From naming conventions to indentation, these practices ensure your EAs and indicators are reliable and scalable.
Test often in MT5’s Strategy Tester, and watch your trading tools shine!
For questions and support please Contact Us.