<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>operator-precedence on toorun.dev</title><link>https://toorun.dev/tags/operator-precedence/</link><description>Recent content in operator-precedence on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 16 Oct 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/operator-precedence/index.xml" rel="self" type="application/rss+xml"/><item><title>Operator Precedence: How Programming Languages Evaluate Expressions</title><link>https://toorun.dev/posts/operator-precedence-how-programming-languages-evaluate-expressions/</link><pubDate>Fri, 16 Oct 2026 09:00:00 +0000</pubDate><guid>https://toorun.dev/posts/operator-precedence-how-programming-languages-evaluate-expressions/</guid><description>Operator Precedence: How Programming Languages Evaluate Expressions What does this expression mean?
2 + 3 * 4 Is the answer 20 or 14?
Most programming languages evaluate multiplication before addition, so the answer is 14. This rule is called operator precedence. It tells the language how to group parts of an expression when parentheses are absent.
Precedence is useful, but it can make long expressions hard to read. In this post, we’ll cover common operators, how expressions are grouped, where languages differ, and how to write code whose meaning is clear.</description></item></channel></rss>