Relational operator

In computer science, a relational operator is a programming language construct or operator that tests or defines some kind of relation between two entities. These include numerical equality (e.g., 5 = 5) and inequalities (e.g., 4 ≥ 3). In programming languages that include a distinct boolean data type in their type system, like Java, these operators return true or false, depending on whether the conditional relationship between the two operands holds or not. In other languages such as C, relational operators return the integers 0 or 1.

An expression created using a relational operator forms what is known as a relational expression or a condition. Relational operators are also used in technical literature instead of words. Relational operators are usually written in infix notation, if supported by the programming language, which means that they appear between their operands (the two expressions being related). For example, an expression in C will print the message if the x is less than y:

  if (x < y) {
      printf("x is less than y in this example\n");
  }

Other programming languages, such as Lisp, use prefix notation, as follows:

(>= X Y)

Standard relational operators

The most common numerical relational operators used in programming languages are shown below.

Common relational operators

Convention	equal to	not equal to	greater than	less than	greater than or equal to	less than or equal to
In print	=	≠	>	<	≥	≤
ALGOL 68	=	≠	>	<	≥	≤
		/=			>=	<=
	eq	ne	gt	lt	ge	le
C-like	==	!=	>	<	>=	<=
BASIC-like	=	<>	>	<	>=	<=
Batch file	EQU	NEQ	GTR	LSS	GEQ	LEQ
Mathematica	==	!=	>	<	>=	<=
	Equal[x,y]	Unequal[x,y]	Greater[x,y]	Less[x,y]	GreaterEqual[x,y]	LessEqual[x,y]
MATLAB	==	~=	>	<	>=	<=
	eq(x,y)	ne(x,y)	gt(x,y)	lt(x,y)	ge(x,y)	le(x,y)
Fortran	==	/=	>	<	>=	<=
	.EQ.	.NE.	.GT.	.LT.	.GE.	.LE.
Bourne-like shells	-eq	-ne	-gt	-lt	-ge	-le
MUMPS	=	'=	>	<	'<	'>

Other conventions are less common: Common Lisp and Macsyma/Maxima use Basic-like operators except for inequality, which is /= in Common Lisp and # in Macsyma/Maxima. Older Lisps used equal, greaterp, and lessp; and negated them using not for the remaining operators.

Equality

Confusion with assignment operators

Early FORTRAN (1956–57) was bounded by heavily restricted character sets where "=" was the only relational operator available. There were no "<" or ">" (and certainly no ≤ or ≥). This forced the designers to define symbols such as .GT., .LT., .GE., .EQ. etc. and subsequently made it tempting to use the remaining "=" character for copying, despite the obvious incoherence with mathematical usage (X=X+1 should be impossible).

International Algebraic Language and ALGOL (1958 and 1960) therefore introduced ":=" for assignment, leaving the standard "=" available for equality, a convention followed by CPL, Algol W, BCPL, Simula, Algol 68, SETL, Pascal, Smalltalk, Modula2, Ada, Standard ML, OCaml, Eiffel, Delphi, Oberon, Dylan, VHDL, and several other languages.

On the other hand, the now very influential language C started off as a minimal compiled language called B, which, in turn, started off as a simplified version of BCPL (a typeless version of CPL). The intented application for B was solely as a vehicle for a first port of (a then very primitive) UNIX. In what that has been described as a "strip-down" process, B replaced the original ":=" and "=" of BCPL by "=" and "==" respectively, the reason for this being unknown (and and or meanwhile became "&" and "|", and later "&&" and "||", respectively). As a small type system was later introduced, B became C. The popularity of C, and its association with UNIX, led to Java, C#, and other languages (including new versions of Fortran) following suit, syntactically, despite this unnecessary conflict with the mathematical meaning of the equal sign.

Languages

Assignments in C have a value and since any non-zero scalar value is interpreted as true in conditional expressions, the code "if (x = y)" is legal, but has a very different meaning from "if (x == y)". The former code fragment means "assign y to x, and if the new value of x is not zero, execute the following statement". The latter fragment means "if and only if x is equal to y, execute the following statement".

  int x = 1;
  int y = 2;
  if (x = y) {
      /* This code will always execute if y is anything but 0*/
      printf("x is %d and y is %d\n", x, y);
  }

Though Java and C# have the same operators as C, this mistake usually causes a compile error in these languages instead, because the if-condition must be of type boolean, and there is no implicit way to convert from other types (e.g. numbers) into booleans. So unless the variable that is assigned to has type boolean (or wrapper type Boolean), there will be a compile error.

In Ada and Python, assignment operators cannot appear in an expression (including if clauses), thus precluding this class of error. Some compilers, such as GCC, will provide a warning when compiling code that contains an assignment operator inside an if statement, though there are some legitimate uses of an assignment inside an if-condition. In those cases the programmer would need to explicitly wrap the assignment in an extra pair of parentheses to avoid the warning.

Similarly, some languages, such as BASIC use just the "=" symbol for both assignment and equality, as they are syntactically separate (as with Ada and Python, assignment operators cannot appear in expressions).

Some programmers get in the habit of writing comparisons against a constant in the reverse of the usual order:

  if (2 == a) {   /* Mistaken use of = versus == would be a compile-time error */
  }

If the programmer accidentally uses =, the resulting code is invalid because 2 is not a variable. The compiler will generate an error message, upon which the proper operator can be substituted. This coding style is known as left-hand comparison.

Object identity vs. Content equality

In many modern programming languages, objects and data structures are accessed through references. In such languages, there becomes a need to test for two different types of equality:

• Physical (or shallow) equality - whether two references reference the same object.
• Structural (or deep) equality - whether the objects referenced by two references are equivalent in some sense (e.g. their contents are the same).

The first type of equality usually implies the second (except for things like NaN which are unequal to themselves), but the converse is not necessarily true. For example, two string objects may be distinct objects (unequal in the first sense) but contain the same sequence of characters (equal in the second sense). See identity for more of this issue.

The following table lists the different mechanisms to test for these two types of equality in various languages:

Language	Physical equality	Structural equality	Notes
ALGOL 68	a :=: b or a is b	a = b	when a and b are pointers
C, C++	a == b	*a == *b	when a and b are pointers
C#	object.ReferenceEquals(a, b)	a.Equals(b)	The == operator defaults to ReferenceEquals, but can be overloaded to perform Equals instead.
Common Lisp	(eq a b)	(equal a b)
Go	a == b	reflect.DeepEqual(*a, *b)	when a and b are pointers
Java	a == b	a.equals(b)
OCaml, Smalltalk	a == b	a = b
Pascal	a^ = b^	a = b
Perl	$a == $b	$$a == $$b	when $a and $b are references to scalars
PHP5	$a === $b	$a == $b	when $a and $b are objects
Python	a is b	a == b
Ruby	a.equal?(b)	a == b
Scheme	(eq? a b)	(equal? a b)
Visual Basic .NET	a Is b	a = b
Objective-C	a == b	[a isEqual:b]	when a and b are pointers to objects that are instances of NSObject

The === operator

The languages JavaScript and PHP extend this syntax, with the "==" operator able to return true if two values are equal, even if they have different types (for example, "4 == "4"" is true), and the "===" operator returning true only if two values are equal and have equivalent types as well (such that "4 === "4"" is false but "4 === 4" is true). This comes in handy when checking if a value is assigned the value of 0, since "x == 0" is true for x being 0, but also for x being "0" (i.e. a string containing the character 0) and false (as PHP, like other languages, equates 0 to false), and that is not always what one wants, but "x === 0" is only true when x is 0. When comparing objects in PHP 5, the "==" operator tests for structural equality, while the "===" operator tests for physical equality.

Logical equivalence

Though perhaps not obvious at first, like the boolean logical operators XOR, AND, OR, and NOT, relational operators can be designed to have logical equivalence, such that they can all be defined in terms of one another. The following four conditional statements all have the same logical equivalence:

• $x<y$
• $y>x$
• $\neg (x\geq y)$
• $\neg (y\leq x)$

See also

• Binary relation
• Common operator notation
• Equality (mathematics)
• Equals sign
• Logical operator
• Operation (mathematics)
• Operator (mathematics)
• Operator (programming)
• Spaceship operator
• Triadic relation