Click here to Skip to main content
Click here to Skip to main content

Inside the Mathematical Expressions Evaluator

, 17 Jan 2008 CPOL
Rate this:
Please Sign up or sign in to vote.
An article on mathematical expression evaluation
Screenshot - insideTheMEE0.gif


Modern calculators solve differential equations and draw plots. They work with trigonometry, hyperbolic, logarithmic, statistic and other functions. Modern calculators contain processors that are much stronger than their predecessors in old "Apollo"-like spaceships. This article describes the easiest way to build a parser with the ability to analyze complex mathematical expressions and evaluate them. The algorithm is the one that is commonly used in the calculators.

Problem Definition

Let's decide what kind of expressions our calculator should handle.

Simple operations: (2+3)*4/5^5
Unary operators: -6
Single functions: 2^3*cos(pi)
Functions with more than one parameter: Log(10,100)
Right-side operators: x!
Variables assignment x=y=10;

Reverse Polish Notation and Shunting Yard Algorithm

A Prefix (Polish) notation was introduced in 1920 by the Polish mathematician Jan Lukasiewicz. It is a mathematical notation wherein every operator follows all of its operands. It is also known as Postfix notation. Reverse Polish notation (RPN) was invented by Australian philosopher and computer scientist Charles Hamblin in the mid-1950s, to enable zero-address memory stores. Hamblin presented his work at a conference in June 1957, and published it in 1957 and 1962.

In Reverse Polish notation, the operators follow their operands. Infix a + b changes to ab+; (a + b)*c changes to ab+c*. One of the RPN advantages is that it obviates the need for parentheses. The main advantage is that it's easy to use RPN with stack (first-in-last-out) structures.

The shunting yard algorithm is a method for parsing mathematical equations specified in infix notation. It can be used to produce output in RPN. The algorithm was invented by Edsger Dijkstra and named the "shunting yard" because its operation resembles that of a railroad shunting yard. Like the evaluation of RPN, the shunting yard algorithm is stack-based. One of the stacks contains operands (digits and variables). Another stack contains all operators (+, -, *, /, etc. and functions that are treated as operators).

Inside the Shunting Yard Algorithm

This is a brief example of how "shunting yard" works. Input expression: (2+3)*4/5;

First of all, we have to push a special "sentinel" operator into the operators stack. The sentinel is used to separate operations inside the parentheses and to indicate the bottom of the stack.

Operands Operators

The parser reads the expression from left to right. The first token is "(" - right parenthesis. The sentinel is pushed into the operators stack. When the parser finishes processing the current token (speaking about any token), it reads the next token, stores it into the "token" variable and processes it.

  • Current token: "2" - an operand. Push it into the operands stack. Read the next token.
  • Current token: "+" - an operator. Push it into the operators stack. Read the next token.
  • Current token: "3" - an operand. Push it into the operands stack. Read the next token.
  • Current token: ")" - right parenthesis. Evaluate both stacks until the sentinel is reached.
Operands Operators
3 +
2 #, parenthesis
#, bottom of the stack

Calculation: Pop "+" from the stack. Compare the operator's precedence. "#" has lower precedence than "+". That's why "+" is processed. "+" is a binary operator; pop two operands ("3" and "2") from the Operands stack. Calculate 2+3 and push the result into the stack. The sentinel (#) is reached. Pop the sentinel from the stack and read the next token.

Operands Operators
5 #
  • Current token: "*" - an operator. Push it into the operators stack. Read the next token.
  • Current token: "4" - an operand. Push it into the operands stack. Read the next token.
  • Current token: "/" - an operator. Compare operators' precedence. "*" has the same precedence as "/". When the token operator's precedence is lower than the stack operator's precedence, the operator in the stack is processed before the current operator.

Calculation: Pop "*" from the stack. Compare the operators' precedence. "#" has lower precedence than "*". "*" is a binary operator; pop "5" and "4" from the operands stack. Calculate 5*4 and push the result back into the stack. Push "/" into the stack. Read the next token: (2+3)*4/5.

  • Current token: "5" - an operand. Push it into the operands stack. Read the next token.
  • The last token is ";" - END indicator. We can process both stacks until the sentinel in the operators stack is reached.
Operands Operators
5 /
20 #

The result is 20/5 = 4

Let's take a look at any simple or complex mathematical expression. We know what kind of token should come first in infix notation. It's a unary operator (like unary minus), left parenthesis, a number or a variable. For instance: -10; a+b; (10-x); The Primary() function converts the current token to one of the described mathematical characters. The binary operator comes after a primary token. The Binary() function evaluates binary operators. We'll also need some subroutine functions like:

  • NextToken() - Reads the next token and stores it to the token variable
  • Precedence() - Returns the operator's precedence
  • ReadOperand() - Parses the sequence of characters or digits to a number, a variable or a function

The beauty of the algorithm in its recursion. A listing below shows the basic algorithm's implementation in pseudo-C#:

   Stack Operands, Operators;
   Token token; // current token

      // Indicates the beginning of the stack

      return Operands.Peek(); //contains the result

      while token is a binary operator
        NextToken();         // read next token

        Primary();           // parse primary

      // while there are operators to evaluate

      while Operators.Peek != Sentinel 
     if token is operand //(digit or char)

     else if token is unary
     else if token is left parenthesis
        Expect (Right parentesis);
        throw exception;
      while Operators.Peek() > op // Precedence()

      if Operators.Peek is binary
         o2 = Operands.Pop();
         o1 = Operands.Pop();
         op = Operators.Pop();
         Operands.Push( Calculate(op, o1, o2) ); 
      else // unary operator

         o1 = Operands.Pop();
         op = Operators.Pop();
         Operands.Push( Calculate(op, o1) );

   private void Expect(expectedToken)
       if (token == expectedToken)
          throw exception

As you can see, the basic implementation is very easy. This scheme is shown in the Basic calculator example.

Variables, Functions and Other Enhancements

Variables and Functions

Let's consider an expression: a+cos(pi) where a and pi are variables and cos is the cosine function. As defined above, the Primary() function is used to parse operands. In general, it should parse names and digits separately. Also, the Name parser should separate variables' and functions' names. The difference between cos(pi) and cosPI is that the first one is a function and the second one is a variable. The trick is that there is no actual "function" concept in this calculator. All functions are treated as operators. For instance, sin(x) is treated as a unary operator and log(x,y) as binary.

Each character sequence that is not a function (x, y1, sinX, etc.) is treated as a variable. The best way to store variables is in a Dictionary <string, double> collection. Therefore if the Primary() function discovers that the current token is a letter, it calls an addition function that reads the whole sequence of characters until an "escape" token is reached. In our example, a is a letter, but the next token is "+". This token cancels reading the sequence. First, the parser checks if "a" is a function or a variable. Then it retrieves "a" from memory (the dictionary) and pushes the value of the "a" variable into the stack.

In the case of a function (in our example, a+cos(pi) ), the parser reads the "c" token and does the same thing as was done with the variable: it reads "c", "o", "s", finds the escape "(" character and locates the cos function in the functions list. Then the parser calls (remember the recursion?) Primary() to parse the function's parameters. For example: cos(pi), log(10, abs( cos(pi) )), etc.

Variables Assignment

Therefore there are stored variables (pi, e) and there should be variables assignment: a=b=10^2. The "=" operator calls Parse() recursively: a=Parse( b=Parse(10^2) )


In mathematical expressions, multiplication is sometimes omitted. For example: the 10*x expression could be replaced with 10x. Let's define all cases in which multiplication could be omitted: x*(y), (y)*x, (y)*(x), x*f(x). When the parser finds a number, a variable or a right parenthesis, it calls the TryInsertMultiply() function that pushes the "*" operator in the stack if multiplication between the tokens was omitted.

Right-side Operators

One of the unary right-side operators in mathematics is the Factorial operator. Factorial is the product of all positive integers from one up to n and including a given integer. Factorial zero is assigned the value of one, factorial n (n!) is 1*2*...*(n-1)*n. To check if the next token is a right-side operator, the TryRightSideOperator() function is called. Argument separators in a multi-argument function are also treated as a right-side operators, i.e. log(2,4).

Power Operation

There is a basic math rule which I had forgotten. The power operator could not be evaluated the same way as multiplication or addition operators are evaluated. 3^4^5 = 3^(4^5), but 3*4*5 = (3*4)*5 or 3*(4*5). This is called associative operation. When the Compare() function compares two power operators, it returns "-1". This means that the current operator (the one that is on the top of the stack) is not processed.

Using the Code

There is one partial class Calculator divided into four files: Parser, Processor, Token and Variable.

  • Parser contains general and parse functions
  • Processor contains math operations' functions
  • Token contains tokens' (operations and functions) constants. It also contains "Is...()" functions, which determine whether the token is a digit, a function, an operator or a variable
  • Variable contains stored variables' subroutines

Points of Interest

The next step is to slightly modify the code and make the calculator able to solve logical expressions.


  • Power operation bug fixed - 15 January 2008
  • Release - 23 October 2007


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Zaur Nasibov
Software Developer
Finland Finland
I'm a Master degree student, studying at the University of Joensuu, Finland.

Comments and Discussions

Questioncan u do the same calculator but it must be on console application PinmemberMember 1107192929-Sep-14 4:28 
GeneralMy vote of 5 PinmemberMassimo Conti3-Jan-13 12:36 
GeneralMy vote of 5 Pinmemberafzal.gujrat20-Oct-12 6:00 
GeneralMy vote of 1 Pinmembervoodooandrew29-Mar-11 12:36 
GeneralRe: My vote of 1 PinmemberSavin Dmitry29-Mar-11 14:12 
GeneralRe: My vote of 1 Pinmembervoodooandrew29-Mar-11 14:31 
GeneralRe: My vote of 1 Pinmemberafzal.gujrat20-Oct-12 6:01 
GeneralParser Speed Pinmemberluiscoco17-Sep-10 8:23 
GeneralExcellent work. My vote of 5 PinmemberHassan3D18-Aug-10 15:06 
GeneralGreat Code - Fix for bug when including negative numbers [modified] PinmemberGregCaine16-Mar-10 18:25 
GeneralSo simple, this is just what I need. PinmemberZaki Alaydrus23-Nov-09 2:20 
Generalเทพจริงๆพี่ Pinmembernew42610-Nov-08 4:23 
GeneralNeed Help. Its URGENT Pinmemberpranav9522-Oct-08 20:01 
QuestionOmit parentheses when applying right-side operators? PinmemberMember 65995127-Sep-08 7:45 
GeneralPrecedence PinmemberHattmannen29-Apr-08 2:04 
GeneralRe: Precedence PinmemberZaur Nasibov29-Apr-08 9:00 
GeneralThere is no evaluation "standard" Pinmemberccs-ed17-Jan-08 11:08 
General[Message Deleted] [modified] PinmemberZaur Nasibov18-Jan-08 2:56 
Generalimperfection PinmemberArnoKalkman30-Dec-07 8:32 
GeneralRe: imperfection PinmemberZaur Nasibov3-Jan-08 1:54 
GeneralNice but PinmemberYoramo24-Nov-07 10:17 
GeneralRe: Nice but PinmemberZaur Nasibov25-Nov-07 4:18 
GeneralExcellent PinmemberSieepvvalk15-Nov-07 10:10 
GeneralVery timely PinprotectorMarc Clifton11-Nov-07 10:25 
GeneralRe: Very timely Pinmemberwarrior_1121-Mar-09 12:25 
GeneralNice- PinmemberJames Brannan5-Nov-07 11:48 
GeneralRe: Nice- PinmemberZaur Nasibov5-Nov-07 21:10 
GeneralNice PinmemberPaul Conrad4-Nov-07 8:50 
GeneralVery Interesting Pinmembermerlin9812-Nov-07 5:03 
GeneralRe: Very Interesting PinmemberZaur Nasibov2-Nov-07 6:36 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.150327.1 | Last Updated 17 Jan 2008
Article Copyright 2007 by Zaur Nasibov
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid