• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How do you write Not equals

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

How do you write "Not equal to" ?

  • ~=

  • !=

  • /=

  • =/=

  • <>

  • &#8800;

  • Other


Results are only viewable after voting.
In my mind, this is somewhat a tempest in a tea pot thread, because human being easily understand the symbol providing they understand the symbol, thus effortlessly handling the concept of inequality. In the USA, I might expect the average 6 year child to understand what = means. But given all the various symbols for inequality, I might not make that same assumption at age 6.

Explaining it to a computer is much harder, and the more precisionion we use, the harder it is. For example if I use an integer has a data type in C, depending on the rounding methods used, 2.45 would be equal to 1.55. And at one time, I was calculating circle circle intersections, had the equations programmed in, and was debugging the program while using the long double data type for all calculations. And testing the tangent intersection at one and only one point. Ad long as I used say, one corcle of radius 1 centered at (0,0) and another circle centered at (3,0) of radius 2, the program returned the correct answerof one and only one point of intersection at (1,0). But as soon as I scaled the same easily solved problem mentally by multiplying up or down, by some fractional multiple, say, 1/2, the program always bombed. And a little debugging showed why. Given the equations I was using, the test for the tangent case, used a quadratic equation where the the test for exact tangent was given by the the square root of quantity B squared minus 4ac equaling exactly zero. But when the computer processed it, even using long doubles, debugging showed the computer making small calculation errors way out at the 18'th digit base 10. And for some reason the computer computed answer was always negative, as the program bombed because there is no solution for the square root of a negative number.

After that it was easy to write an error handler, and tell the computer if the difference between the numbers were less that 10 to the minus 17, assume they are equal.
 
Last edited:
i type != for not equals, but i type ~= for roughly equals, or approximately equals D:

am i doing it wrong?
 
Excel
Equals (=)
Less than (<)
Less than or equal to (<=)
Greater than (>)
Greater than or equal to (>=)
Not equal to (<>)

C#
== Equal
!= Not equal
> Greater than
>= Greater than or equal to
< Less than
<= Less than or equal to

Mathematical Symbols
&#8800; not equal
< less than
> greater than
&#8804; less than or equal to
&#8805; greater than or equal to

Matlab/Octave
~=

One of the oldest ones
<>
 
Excel
Equals (=)
Less than (<)
Less than or equal to (<=)
Greater than (>)
Greater than or equal to (>=)
Not equal to (<>)

C#
== Equal
!= Not equal
> Greater than
>= Greater than or equal to
< Less than
<= Less than or equal to

Mathematical Symbols
&#8800; not equal
< less than
> greater than
&#8804; less than or equal to
&#8805; greater than or equal to

Matlab/Octave
~=

One of the oldest ones
<>

A~=~!=a
 
I started with BASIC, so <> used to make sense. Haven't done BASIC in a long time, and I've grown to like != better anyway...because you can also do !(condition) for true/false (boolean) stuff.
 
Technically speaking, the answer to the question is, within the context of computer use,:
notequal12441.png
 
Back
Top