2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990-1995, 1998-1999, 2001-2012
4 @c Free Software Foundation, Inc.
5 @c See the file elisp.texi for copying conditions.
6 @setfilename ../../info/numbers
7 @node Numbers, Strings and Characters, Lisp Data Types, Top
12 GNU Emacs supports two numeric data types: @dfn{integers} and
13 @dfn{floating point numbers}. Integers are whole numbers such as
14 @minus{}3, 0, 7, 13, and 511. Their values are exact. Floating point
15 numbers are numbers with fractional parts, such as @minus{}4.5, 0.0, or
16 2.71828. They can also be expressed in exponential notation: 1.5e2
17 equals 150; in this example, @samp{e2} stands for ten to the second
18 power, and that is multiplied by 1.5. Floating point values are not
19 exact; they have a fixed, limited amount of precision.
22 * Integer Basics:: Representation and range of integers.
23 * Float Basics:: Representation and range of floating point.
24 * Predicates on Numbers:: Testing for numbers.
25 * Comparison of Numbers:: Equality and inequality predicates.
26 * Numeric Conversions:: Converting float to integer and vice versa.
27 * Arithmetic Operations:: How to add, subtract, multiply and divide.
28 * Rounding Operations:: Explicitly rounding floating point numbers.
29 * Bitwise Operations:: Logical and, or, not, shifting.
30 * Math Functions:: Trig, exponential and logarithmic functions.
31 * Random Numbers:: Obtaining random integers, predictable or not.
35 @comment node-name, next, previous, up
36 @section Integer Basics
38 The range of values for an integer depends on the machine. The
39 minimum range is @minus{}536870912 to 536870911 (30 bits; i.e.,
53 but some machines provide a wider range. Many examples in this
54 chapter assume that an integer has 30 bits and that floating point
55 numbers are IEEE double precision.
58 The Lisp reader reads an integer as a sequence of digits with optional
59 initial sign and optional final period. An integer that is out of the
60 Emacs range is treated as a floating-point number.
63 1 ; @r{The integer 1.}
64 1. ; @r{The integer 1.}
65 +1 ; @r{Also the integer 1.}
66 -1 ; @r{The integer @minus{}1.}
67 1073741825 ; @r{The floating point number 1073741825.0.}
68 0 ; @r{The integer 0.}
69 -0 ; @r{The integer 0.}
72 @cindex integers in specific radix
73 @cindex radix for reading an integer
74 @cindex base for reading an integer
77 @cindex reading numbers in hex, octal, and binary
78 The syntax for integers in bases other than 10 uses @samp{#}
79 followed by a letter that specifies the radix: @samp{b} for binary,
80 @samp{o} for octal, @samp{x} for hex, or @samp{@var{radix}r} to
81 specify radix @var{radix}. Case is not significant for the letter
82 that specifies the radix. Thus, @samp{#b@var{integer}} reads
83 @var{integer} in binary, and @samp{#@var{radix}r@var{integer}} reads
84 @var{integer} in radix @var{radix}. Allowed values of @var{radix} run
85 from 2 to 36. For example:
94 To understand how various functions work on integers, especially the
95 bitwise operators (@pxref{Bitwise Operations}), it is often helpful to
96 view the numbers in their binary form.
98 In 30-bit binary, the decimal integer 5 looks like this:
101 0000...000101 (30 bits total)
105 (The @samp{...} stands for enough bits to fill out a 30-bit word; in
106 this case, @samp{...} stands for twenty 0 bits. Later examples also
107 use the @samp{...} notation to make binary integers easier to read.)
109 The integer @minus{}1 looks like this:
112 1111...111111 (30 bits total)
116 @cindex two's complement
117 @minus{}1 is represented as 30 ones. (This is called @dfn{two's
118 complement} notation.)
120 The negative integer, @minus{}5, is creating by subtracting 4 from
121 @minus{}1. In binary, the decimal integer 4 is 100. Consequently,
122 @minus{}5 looks like this:
125 1111...111011 (30 bits total)
128 In this implementation, the largest 30-bit binary integer value is
129 536,870,911 in decimal. In binary, it looks like this:
132 0111...111111 (30 bits total)
135 Since the arithmetic functions do not check whether integers go
136 outside their range, when you add 1 to 536,870,911, the value is the
137 negative integer @minus{}536,870,912:
142 @result{} 1000...000000 (30 bits total)
145 Many of the functions described in this chapter accept markers for
146 arguments in place of numbers. (@xref{Markers}.) Since the actual
147 arguments to such functions may be either numbers or markers, we often
148 give these arguments the name @var{number-or-marker}. When the argument
149 value is a marker, its position value is used and its buffer is ignored.
151 @cindex largest Lisp integer number
152 @cindex maximum Lisp integer number
153 @defvar most-positive-fixnum
154 The value of this variable is the largest integer that Emacs Lisp
158 @cindex smallest Lisp integer number
159 @cindex minimum Lisp integer number
160 @defvar most-negative-fixnum
161 The value of this variable is the smallest integer that Emacs Lisp can
162 handle. It is negative.
165 @xref{Character Codes, max-char}, for the maximum value of a valid
169 @section Floating Point Basics
171 @cindex @acronym{IEEE} floating point
172 Floating point numbers are useful for representing numbers that are
173 not integral. The precise range of floating point numbers is
174 machine-specific; it is the same as the range of the C data type
175 @code{double} on the machine you are using. Emacs uses the
176 @acronym{IEEE} floating point standard where possible (the standard is
177 supported by most modern computers).
179 The read syntax for floating point numbers requires either a decimal
180 point (with at least one digit following), an exponent, or both. For
181 example, @samp{1500.0}, @samp{15e2}, @samp{15.0e2}, @samp{1.5e3}, and
182 @samp{.15e4} are five ways of writing a floating point number whose
183 value is 1500. They are all equivalent. You can also use a minus
184 sign to write negative floating point numbers, as in @samp{-1.0}.
186 Emacs Lisp treats @code{-0.0} as equal to ordinary zero (with
187 respect to @code{equal} and @code{=}), even though the two are
188 distinguishable in the @acronym{IEEE} floating point standard.
190 @cindex positive infinity
191 @cindex negative infinity
194 The @acronym{IEEE} floating point standard supports positive
195 infinity and negative infinity as floating point values. It also
196 provides for a class of values called NaN or ``not-a-number'';
197 numerical functions return such values in cases where there is no
198 correct answer. For example, @code{(/ 0.0 0.0)} returns a NaN. (NaN
199 values can also carry a sign, but for practical purposes there's no
200 significant difference between different NaN values in Emacs Lisp.)
201 Here are the read syntaxes for these special floating point values:
204 @item positive infinity
206 @item negative infinity
209 @samp{0.0e+NaN} or @samp{-0.0e+NaN}.
213 This predicate tests whether its argument is NaN, and returns @code{t}
214 if so, @code{nil} otherwise. The argument must be a number.
217 The following functions are specialized for handling floating point
221 This function returns a cons cell @code{(@var{sig} . @var{exp})},
222 where @var{sig} and @var{exp} are respectively the significand and
223 exponent of the floating point number @var{x}:
226 @var{x} = @var{sig} * 2^@var{exp}
229 @var{sig} is a floating point number between 0.5 (inclusive) and 1.0
230 (exclusive). If @var{x} is zero, the return value is @code{(0 . 0)}.
233 @defun ldexp sig &optional exp
234 This function returns a floating point number corresponding to the
235 significand @var{sig} and exponent @var{exp}.
238 @defun copysign x1 x2
239 This function copies the sign of @var{x2} to the value of @var{x1},
240 and returns the result. @var{x1} and @var{x2} must be floating point
245 This function returns the binary exponent of @var{number}. More
246 precisely, the value is the logarithm of @var{number} base 2, rounded
257 @node Predicates on Numbers
258 @section Type Predicates for Numbers
259 @cindex predicates for numbers
261 The functions in this section test for numbers, or for a specific
262 type of number. The functions @code{integerp} and @code{floatp} can
263 take any type of Lisp object as argument (they would not be of much
264 use otherwise), but the @code{zerop} predicate requires a number as
265 its argument. See also @code{integer-or-marker-p} and
266 @code{number-or-marker-p}, in @ref{Predicates on Markers}.
269 This predicate tests whether its argument is a floating point
270 number and returns @code{t} if so, @code{nil} otherwise.
272 @code{floatp} does not exist in Emacs versions 18 and earlier.
275 @defun integerp object
276 This predicate tests whether its argument is an integer, and returns
277 @code{t} if so, @code{nil} otherwise.
280 @defun numberp object
281 This predicate tests whether its argument is a number (either integer or
282 floating point), and returns @code{t} if so, @code{nil} otherwise.
285 @defun natnump object
286 @cindex natural numbers
287 This predicate (whose name comes from the phrase ``natural number'')
288 tests to see whether its argument is a nonnegative integer, and
289 returns @code{t} if so, @code{nil} otherwise. 0 is considered
292 @findex wholenump number
293 This is a synonym for @code{natnump}.
297 This predicate tests whether its argument is zero, and returns @code{t}
298 if so, @code{nil} otherwise. The argument must be a number.
300 @code{(zerop x)} is equivalent to @code{(= x 0)}.
303 @node Comparison of Numbers
304 @section Comparison of Numbers
305 @cindex number comparison
306 @cindex comparing numbers
308 To test numbers for numerical equality, you should normally use
309 @code{=}, not @code{eq}. There can be many distinct floating point
310 number objects with the same numeric value. If you use @code{eq} to
311 compare them, then you test whether two values are the same
312 @emph{object}. By contrast, @code{=} compares only the numeric values
315 At present, each integer value has a unique Lisp object in Emacs Lisp.
316 Therefore, @code{eq} is equivalent to @code{=} where integers are
317 concerned. It is sometimes convenient to use @code{eq} for comparing an
318 unknown value with an integer, because @code{eq} does not report an
319 error if the unknown value is not a number---it accepts arguments of any
320 type. By contrast, @code{=} signals an error if the arguments are not
321 numbers or markers. However, it is a good idea to use @code{=} if you
322 can, even for comparing integers, just in case we change the
323 representation of integers in a future Emacs version.
325 Sometimes it is useful to compare numbers with @code{equal}; it
326 treats two numbers as equal if they have the same data type (both
327 integers, or both floating point) and the same value. By contrast,
328 @code{=} can treat an integer and a floating point number as equal.
329 @xref{Equality Predicates}.
331 There is another wrinkle: because floating point arithmetic is not
332 exact, it is often a bad idea to check for equality of two floating
333 point values. Usually it is better to test for approximate equality.
334 Here's a function to do this:
337 (defvar fuzz-factor 1.0e-6)
338 (defun approx-equal (x y)
339 (or (and (= x 0) (= y 0))
341 (max (abs x) (abs y)))
345 @cindex CL note---integers vrs @code{eq}
347 @b{Common Lisp note:} Comparing numbers in Common Lisp always requires
348 @code{=} because Common Lisp implements multi-word integers, and two
349 distinct integer objects can have the same numeric value. Emacs Lisp
350 can have just one integer object for any given value because it has a
351 limited range of integer values.
354 @defun = number-or-marker1 number-or-marker2
355 This function tests whether its arguments are numerically equal, and
356 returns @code{t} if so, @code{nil} otherwise.
359 @defun eql value1 value2
360 This function acts like @code{eq} except when both arguments are
361 numbers. It compares numbers by type and numeric value, so that
362 @code{(eql 1.0 1)} returns @code{nil}, but @code{(eql 1.0 1.0)} and
363 @code{(eql 1 1)} both return @code{t}.
366 @defun /= number-or-marker1 number-or-marker2
367 This function tests whether its arguments are numerically equal, and
368 returns @code{t} if they are not, and @code{nil} if they are.
371 @defun < number-or-marker1 number-or-marker2
372 This function tests whether its first argument is strictly less than
373 its second argument. It returns @code{t} if so, @code{nil} otherwise.
376 @defun <= number-or-marker1 number-or-marker2
377 This function tests whether its first argument is less than or equal
378 to its second argument. It returns @code{t} if so, @code{nil}
382 @defun > number-or-marker1 number-or-marker2
383 This function tests whether its first argument is strictly greater
384 than its second argument. It returns @code{t} if so, @code{nil}
388 @defun >= number-or-marker1 number-or-marker2
389 This function tests whether its first argument is greater than or
390 equal to its second argument. It returns @code{t} if so, @code{nil}
394 @defun max number-or-marker &rest numbers-or-markers
395 This function returns the largest of its arguments.
396 If any of the arguments is floating-point, the value is returned
397 as floating point, even if it was given as an integer.
409 @defun min number-or-marker &rest numbers-or-markers
410 This function returns the smallest of its arguments.
411 If any of the arguments is floating-point, the value is returned
412 as floating point, even if it was given as an integer.
421 This function returns the absolute value of @var{number}.
424 @node Numeric Conversions
425 @section Numeric Conversions
426 @cindex rounding in conversions
427 @cindex number conversions
428 @cindex converting numbers
430 To convert an integer to floating point, use the function @code{float}.
433 This returns @var{number} converted to floating point.
434 If @var{number} is already a floating point number, @code{float} returns
438 There are four functions to convert floating point numbers to integers;
439 they differ in how they round. All accept an argument @var{number}
440 and an optional argument @var{divisor}. Both arguments may be
441 integers or floating point numbers. @var{divisor} may also be
442 @code{nil}. If @var{divisor} is @code{nil} or omitted, these
443 functions convert @var{number} to an integer, or return it unchanged
444 if it already is an integer. If @var{divisor} is non-@code{nil}, they
445 divide @var{number} by @var{divisor} and convert the result to an
446 integer. An @code{arith-error} results if @var{divisor} is 0.
448 @defun truncate number &optional divisor
449 This returns @var{number}, converted to an integer by rounding towards
464 @defun floor number &optional divisor
465 This returns @var{number}, converted to an integer by rounding downward
466 (towards negative infinity).
468 If @var{divisor} is specified, this uses the kind of division
469 operation that corresponds to @code{mod}, rounding downward.
485 @defun ceiling number &optional divisor
486 This returns @var{number}, converted to an integer by rounding upward
487 (towards positive infinity).
501 @defun round number &optional divisor
502 This returns @var{number}, converted to an integer by rounding towards the
503 nearest integer. Rounding a value equidistant between two integers
504 may choose the integer closer to zero, or it may prefer an even integer,
505 depending on your machine.
519 @node Arithmetic Operations
520 @section Arithmetic Operations
521 @cindex arithmetic operations
523 Emacs Lisp provides the traditional four arithmetic operations:
524 addition, subtraction, multiplication, and division. Remainder and modulus
525 functions supplement the division functions. The functions to
526 add or subtract 1 are provided because they are traditional in Lisp and
529 All of these functions except @code{%} return a floating point value
530 if any argument is floating.
532 It is important to note that in Emacs Lisp, arithmetic functions
533 do not check for overflow. Thus @code{(1+ 536870911)} may evaluate to
534 @minus{}536870912, depending on your hardware.
536 @defun 1+ number-or-marker
537 This function returns @var{number-or-marker} plus 1.
547 This function is not analogous to the C operator @code{++}---it does not
548 increment a variable. It just computes a sum. Thus, if we continue,
555 If you want to increment the variable, you must use @code{setq},
564 @defun 1- number-or-marker
565 This function returns @var{number-or-marker} minus 1.
568 @defun + &rest numbers-or-markers
569 This function adds its arguments together. When given no arguments,
582 @defun - &optional number-or-marker &rest more-numbers-or-markers
583 The @code{-} function serves two purposes: negation and subtraction.
584 When @code{-} has a single argument, the value is the negative of the
585 argument. When there are multiple arguments, @code{-} subtracts each of
586 the @var{more-numbers-or-markers} from @var{number-or-marker},
587 cumulatively. If there are no arguments, the result is 0.
599 @defun * &rest numbers-or-markers
600 This function multiplies its arguments together, and returns the
601 product. When given no arguments, @code{*} returns 1.
613 @defun / dividend divisor &rest divisors
614 This function divides @var{dividend} by @var{divisor} and returns the
615 quotient. If there are additional arguments @var{divisors}, then it
616 divides @var{dividend} by each divisor in turn. Each argument may be a
619 If all the arguments are integers, then the result is an integer too.
620 This means the result has to be rounded. On most machines, the result
621 is rounded towards zero after each division, but some machines may round
622 differently with negative arguments. This is because the Lisp function
623 @code{/} is implemented using the C division operator, which also
624 permits machine-dependent rounding. As a practical matter, all known
625 machines round in the standard fashion.
627 @cindex @code{arith-error} in division
628 If you divide an integer by 0, an @code{arith-error} error is signaled.
629 (@xref{Errors}.) Floating point division by zero returns either
630 infinity or a NaN if your machine supports @acronym{IEEE} floating point;
631 otherwise, it signals an @code{arith-error} error.
650 @result{} -2 @r{(could in theory be @minus{}3 on some machines)}
655 @defun % dividend divisor
657 This function returns the integer remainder after division of @var{dividend}
658 by @var{divisor}. The arguments must be integers or markers.
660 For negative arguments, the remainder is in principle machine-dependent
661 since the quotient is; but in practice, all known machines behave alike.
663 An @code{arith-error} results if @var{divisor} is 0.
676 For any two integers @var{dividend} and @var{divisor},
680 (+ (% @var{dividend} @var{divisor})
681 (* (/ @var{dividend} @var{divisor}) @var{divisor}))
686 always equals @var{dividend}.
689 @defun mod dividend divisor
691 This function returns the value of @var{dividend} modulo @var{divisor};
692 in other words, the remainder after division of @var{dividend}
693 by @var{divisor}, but with the same sign as @var{divisor}.
694 The arguments must be numbers or markers.
696 Unlike @code{%}, @code{mod} returns a well-defined result for negative
697 arguments. It also permits floating point arguments; it rounds the
698 quotient downward (towards minus infinity) to an integer, and uses that
699 quotient to compute the remainder.
701 An @code{arith-error} results if @var{divisor} is 0.
726 For any two numbers @var{dividend} and @var{divisor},
730 (+ (mod @var{dividend} @var{divisor})
731 (* (floor @var{dividend} @var{divisor}) @var{divisor}))
736 always equals @var{dividend}, subject to rounding error if either
737 argument is floating point. For @code{floor}, see @ref{Numeric
741 @node Rounding Operations
742 @section Rounding Operations
743 @cindex rounding without conversion
745 The functions @code{ffloor}, @code{fceiling}, @code{fround}, and
746 @code{ftruncate} take a floating point argument and return a floating
747 point result whose value is a nearby integer. @code{ffloor} returns the
748 nearest integer below; @code{fceiling}, the nearest integer above;
749 @code{ftruncate}, the nearest integer in the direction towards zero;
750 @code{fround}, the nearest integer.
753 This function rounds @var{float} to the next lower integral value, and
754 returns that value as a floating point number.
757 @defun fceiling float
758 This function rounds @var{float} to the next higher integral value, and
759 returns that value as a floating point number.
762 @defun ftruncate float
763 This function rounds @var{float} towards zero to an integral value, and
764 returns that value as a floating point number.
768 This function rounds @var{float} to the nearest integral value,
769 and returns that value as a floating point number.
772 @node Bitwise Operations
773 @section Bitwise Operations on Integers
774 @cindex bitwise arithmetic
775 @cindex logical arithmetic
777 In a computer, an integer is represented as a binary number, a
778 sequence of @dfn{bits} (digits which are either zero or one). A bitwise
779 operation acts on the individual bits of such a sequence. For example,
780 @dfn{shifting} moves the whole sequence left or right one or more places,
781 reproducing the same pattern ``moved over''.
783 The bitwise operations in Emacs Lisp apply only to integers.
785 @defun lsh integer1 count
786 @cindex logical shift
787 @code{lsh}, which is an abbreviation for @dfn{logical shift}, shifts the
788 bits in @var{integer1} to the left @var{count} places, or to the right
789 if @var{count} is negative, bringing zeros into the vacated bits. If
790 @var{count} is negative, @code{lsh} shifts zeros into the leftmost
791 (most-significant) bit, producing a positive result even if
792 @var{integer1} is negative. Contrast this with @code{ash}, below.
794 Here are two examples of @code{lsh}, shifting a pattern of bits one
795 place to the left. We show only the low-order eight bits of the binary
796 pattern; the rest are all zero.
802 ;; @r{Decimal 5 becomes decimal 10.}
803 00000101 @result{} 00001010
807 ;; @r{Decimal 7 becomes decimal 14.}
808 00000111 @result{} 00001110
813 As the examples illustrate, shifting the pattern of bits one place to
814 the left produces a number that is twice the value of the previous
817 Shifting a pattern of bits two places to the left produces results
818 like this (with 8-bit binary numbers):
824 ;; @r{Decimal 3 becomes decimal 12.}
825 00000011 @result{} 00001100
829 On the other hand, shifting one place to the right looks like this:
835 ;; @r{Decimal 6 becomes decimal 3.}
836 00000110 @result{} 00000011
842 ;; @r{Decimal 5 becomes decimal 2.}
843 00000101 @result{} 00000010
848 As the example illustrates, shifting one place to the right divides the
849 value of a positive integer by two, rounding downward.
851 The function @code{lsh}, like all Emacs Lisp arithmetic functions, does
852 not check for overflow, so shifting left can discard significant bits
853 and change the sign of the number. For example, left shifting
854 536,870,911 produces @minus{}2 in the 30-bit implementation:
857 (lsh 536870911 1) ; @r{left shift}
861 In binary, the argument looks like this:
865 ;; @r{Decimal 536,870,911}
866 0111...111111 (30 bits total)
871 which becomes the following when left shifted:
875 ;; @r{Decimal @minus{}2}
876 1111...111110 (30 bits total)
881 @defun ash integer1 count
882 @cindex arithmetic shift
883 @code{ash} (@dfn{arithmetic shift}) shifts the bits in @var{integer1}
884 to the left @var{count} places, or to the right if @var{count}
887 @code{ash} gives the same results as @code{lsh} except when
888 @var{integer1} and @var{count} are both negative. In that case,
889 @code{ash} puts ones in the empty bit positions on the left, while
890 @code{lsh} puts zeros in those bit positions.
892 Thus, with @code{ash}, shifting the pattern of bits one place to the right
897 (ash -6 -1) @result{} -3
898 ;; @r{Decimal @minus{}6 becomes decimal @minus{}3.}
899 1111...111010 (30 bits total)
901 1111...111101 (30 bits total)
905 In contrast, shifting the pattern of bits one place to the right with
906 @code{lsh} looks like this:
910 (lsh -6 -1) @result{} 536870909
911 ;; @r{Decimal @minus{}6 becomes decimal 536,870,909.}
912 1111...111010 (30 bits total)
914 0111...111101 (30 bits total)
918 Here are other examples:
920 @c !!! Check if lined up in smallbook format! XDVI shows problem
921 @c with smallbook but not with regular book! --rjc 16mar92
924 ; @r{ 30-bit binary values}
926 (lsh 5 2) ; 5 = @r{0000...000101}
927 @result{} 20 ; = @r{0000...010100}
932 (lsh -5 2) ; -5 = @r{1111...111011}
933 @result{} -20 ; = @r{1111...101100}
938 (lsh 5 -2) ; 5 = @r{0000...000101}
939 @result{} 1 ; = @r{0000...000001}
946 (lsh -5 -2) ; -5 = @r{1111...111011}
948 ; = @r{0011...111110}
951 (ash -5 -2) ; -5 = @r{1111...111011}
952 @result{} -2 ; = @r{1111...111110}
957 @defun logand &rest ints-or-markers
958 This function returns the ``logical and'' of the arguments: the
959 @var{n}th bit is set in the result if, and only if, the @var{n}th bit is
960 set in all the arguments. (``Set'' means that the value of the bit is 1
963 For example, using 4-bit binary numbers, the ``logical and'' of 13 and
964 12 is 12: 1101 combined with 1100 produces 1100.
965 In both the binary numbers, the leftmost two bits are set (i.e., they
966 are 1's), so the leftmost two bits of the returned value are set.
967 However, for the rightmost two bits, each is zero in at least one of
968 the arguments, so the rightmost two bits of the returned value are 0's.
980 If @code{logand} is not passed any argument, it returns a value of
981 @minus{}1. This number is an identity element for @code{logand}
982 because its binary representation consists entirely of ones. If
983 @code{logand} is passed just one argument, it returns that argument.
987 ; @r{ 30-bit binary values}
989 (logand 14 13) ; 14 = @r{0000...001110}
990 ; 13 = @r{0000...001101}
991 @result{} 12 ; 12 = @r{0000...001100}
995 (logand 14 13 4) ; 14 = @r{0000...001110}
996 ; 13 = @r{0000...001101}
997 ; 4 = @r{0000...000100}
998 @result{} 4 ; 4 = @r{0000...000100}
1003 @result{} -1 ; -1 = @r{1111...111111}
1008 @defun logior &rest ints-or-markers
1009 This function returns the ``inclusive or'' of its arguments: the @var{n}th bit
1010 is set in the result if, and only if, the @var{n}th bit is set in at least
1011 one of the arguments. If there are no arguments, the result is zero,
1012 which is an identity element for this operation. If @code{logior} is
1013 passed just one argument, it returns that argument.
1017 ; @r{ 30-bit binary values}
1019 (logior 12 5) ; 12 = @r{0000...001100}
1020 ; 5 = @r{0000...000101}
1021 @result{} 13 ; 13 = @r{0000...001101}
1025 (logior 12 5 7) ; 12 = @r{0000...001100}
1026 ; 5 = @r{0000...000101}
1027 ; 7 = @r{0000...000111}
1028 @result{} 15 ; 15 = @r{0000...001111}
1033 @defun logxor &rest ints-or-markers
1034 This function returns the ``exclusive or'' of its arguments: the
1035 @var{n}th bit is set in the result if, and only if, the @var{n}th bit is
1036 set in an odd number of the arguments. If there are no arguments, the
1037 result is 0, which is an identity element for this operation. If
1038 @code{logxor} is passed just one argument, it returns that argument.
1042 ; @r{ 30-bit binary values}
1044 (logxor 12 5) ; 12 = @r{0000...001100}
1045 ; 5 = @r{0000...000101}
1046 @result{} 9 ; 9 = @r{0000...001001}
1050 (logxor 12 5 7) ; 12 = @r{0000...001100}
1051 ; 5 = @r{0000...000101}
1052 ; 7 = @r{0000...000111}
1053 @result{} 14 ; 14 = @r{0000...001110}
1058 @defun lognot integer
1059 This function returns the logical complement of its argument: the @var{n}th
1060 bit is one in the result if, and only if, the @var{n}th bit is zero in
1061 @var{integer}, and vice-versa.
1066 ;; 5 = @r{0000...000101} (30 bits total)
1068 ;; -6 = @r{1111...111010} (30 bits total)
1072 @node Math Functions
1073 @section Standard Mathematical Functions
1074 @cindex transcendental functions
1075 @cindex mathematical functions
1076 @cindex floating-point functions
1078 These mathematical functions allow integers as well as floating point
1079 numbers as arguments.
1084 These are the ordinary trigonometric functions, with argument measured
1089 The value of @code{(asin @var{arg})} is a number between
1103 (inclusive) whose sine is @var{arg}; if, however, @var{arg} is out of
1104 range (outside [@minus{}1, 1]), it signals a @code{domain-error} error.
1108 The value of @code{(acos @var{arg})} is a number between 0 and
1115 (inclusive) whose cosine is @var{arg}; if, however, @var{arg} is out
1116 of range (outside [@minus{}1, 1]), it signals a @code{domain-error} error.
1119 @defun atan y &optional x
1120 The value of @code{(atan @var{y})} is a number between
1134 (exclusive) whose tangent is @var{y}. If the optional second
1135 argument @var{x} is given, the value of @code{(atan y x)} is the
1136 angle in radians between the vector @code{[@var{x}, @var{y}]} and the
1141 This is the exponential function; it returns @math{e} to the power
1145 @defun log arg &optional base
1146 This function returns the logarithm of @var{arg}, with base
1147 @var{base}. If you don't specify @var{base}, the natural base
1148 @math{e} is used. If @var{arg} is negative, it signals a
1149 @code{domain-error} error.
1154 This function returns @code{(1- (exp @var{arg}))}, but it is more
1155 accurate than that when @var{arg} is negative and @code{(exp @var{arg})}
1160 This function returns @code{(log (1+ @var{arg}))}, but it is more
1161 accurate than that when @var{arg} is so small that adding 1 to it would
1167 This function returns the logarithm of @var{arg}, with base 10. If
1168 @var{arg} is negative, it signals a @code{domain-error} error.
1169 @code{(log10 @var{x})} @equiv{} @code{(log @var{x} 10)}, at least
1174 This function returns @var{x} raised to power @var{y}. If both
1175 arguments are integers and @var{y} is positive, the result is an
1176 integer; in this case, overflow causes truncation, so watch out.
1180 This returns the square root of @var{arg}. If @var{arg} is negative,
1181 it signals a @code{domain-error} error.
1184 In addition, Emacs defines the following common mathematical
1188 The mathematical constant @math{e} (2.71828@dots{}).
1192 The mathematical constant @math{pi} (3.14159@dots{}).
1195 @node Random Numbers
1196 @section Random Numbers
1197 @cindex random numbers
1199 A deterministic computer program cannot generate true random numbers.
1200 For most purposes, @dfn{pseudo-random numbers} suffice. A series of
1201 pseudo-random numbers is generated in a deterministic fashion. The
1202 numbers are not truly random, but they have certain properties that
1203 mimic a random series. For example, all possible values occur equally
1204 often in a pseudo-random series.
1206 In Emacs, pseudo-random numbers are generated from a ``seed'' number.
1207 Starting from any given seed, the @code{random} function always
1208 generates the same sequence of numbers. Emacs always starts with the
1209 same seed value, so the sequence of values of @code{random} is actually
1210 the same in each Emacs run! For example, in one operating system, the
1211 first call to @code{(random)} after you start Emacs always returns
1212 @minus{}1457731, and the second one always returns @minus{}7692030. This
1213 repeatability is helpful for debugging.
1215 If you want random numbers that don't always come out the same, execute
1216 @code{(random t)}. This chooses a new seed based on the current time of
1217 day and on Emacs's process @acronym{ID} number.
1219 @defun random &optional limit
1220 This function returns a pseudo-random integer. Repeated calls return a
1221 series of pseudo-random integers.
1223 If @var{limit} is a positive integer, the value is chosen to be
1224 nonnegative and less than @var{limit}.
1226 If @var{limit} is @code{t}, it means to choose a new seed based on the
1227 current time of day and on Emacs's process @acronym{ID} number.
1229 On some machines, any integer representable in Lisp may be the result
1230 of @code{random}. On other machines, the result can never be larger
1231 than a certain maximum or less than a certain (negative) minimum.