PEMDAS in Java: Order of Operations Explained with Examples

PEMDAS is a mnemonic for the order of operations in arithmetic. It ensures calculations are performed consistently. In Java, it governs how expressions like 5 + 3 * 2 are evaluated. Let’s break it down!

PEMDAS Breakdown

P – Parentheses ()

Highest precedence. Operations inside parentheses are evaluated first.

int result = (10 + 5) * 2; // 15 * 2 = 30  

E – Exponents

Java doesn’t have a built-in exponent operator. Use Math.pow() instead:

double power = Math.pow(2, 3); // 8.0 (2³)  

M/D – Multiplication * / Division /

Equal precedence. Evaluated left to right.

int x = 10 / 2 * 5; // (10/2)=5 → 5*5=25  

A/S – Addition + / Subtraction -**

Equal precedence. Evaluated left to right.

int y = 20 - 5 + 3; // (20-5)=15 → 15+3=18  

PEMDAS in Java: Examples

Example 1: Basic Arithmetic

int result = 5 + 3 * 2; // 3*2=6 → 5+6=11  

Example 2: Parentheses Override

int result = (5 + 3) * 2; // 8*2=16  

Example 3: Division vs. Multiplication

int result = 10 / 2 * 5; // 5*5=25 (not 10/(2*5)=1)  

Example 4: Modulus Operator (%)

Same precedence as multiplication/division:

int value = 10 + 15 % 4; // 15%4=3 → 10+3=13  

Common Mistakes to Avoid

Ignoring integer division

double avg = (5 + 3) / 2; // Result: 4.0 (not 4.5)  
// Fix:  
double avg = (5 + 3) / 2.0; // 4.5  

Misplacing operations

int result = 5 + 2 * 3; // 11 (not 21)  

Forgetting parentheses

boolean isEven = 10 % 2 == 0; // Correct  
boolean isEven = (10 % 2) == 0; // Better for clarity  

Java Operator Precedence Table (Simplified)

Why PEMDAS Matters in Java

• Ensures calculations are predictable.
• Prevents logical errors in math-heavy code (e.g., financial apps).
• Improves readability when used with parentheses.