manual:chapter3:reals

# Differences

This shows you the differences between two versions of the page.

 manual:chapter3:reals [2017/06/11 17:02]smartin created manual:chapter3:reals [2019/11/06 15:21] (current)jojo1973 Added Special symbols 2019/11/06 15:21 jojo1973 Added Special symbols2019/11/05 16:32 jojo1973 Added more commands2019/11/04 16:06 jojo1973 More reformatting2019/11/04 15:38 jojo1973 Reformatted2019/10/16 09:32 claudio [Numbers in other bases] 2019/10/16 09:32 claudio [Numbers in other bases] 2019/06/24 13:18 claudio [Bit operations] 2019/06/24 13:16 claudio [Numbers in other bases] 2017/06/17 13:38 smartin [Numbers] 2017/06/15 18:50 smartin [Approximate versus Exact] 2017/06/11 17:46 smartin [Numbers in other bases] 2017/06/11 17:45 smartin [Setting the word size] 2017/06/11 17:42 smartin 2017/06/11 17:32 smartin [Numbers in other bases] 2017/06/11 17:24 smartin [Exact versus Approximate] 2017/06/11 17:23 smartin 2017/06/11 17:02 smartin created 2019/11/06 15:21 jojo1973 Added Special symbols2019/11/05 16:32 jojo1973 Added more commands2019/11/04 16:06 jojo1973 More reformatting2019/11/04 15:38 jojo1973 Reformatted2019/10/16 09:32 claudio [Numbers in other bases] 2019/10/16 09:32 claudio [Numbers in other bases] 2019/06/24 13:18 claudio [Bit operations] 2019/06/24 13:16 claudio [Numbers in other bases] 2017/06/17 13:38 smartin [Numbers] 2017/06/15 18:50 smartin [Approximate versus Exact] 2017/06/11 17:46 smartin [Numbers in other bases] 2017/06/11 17:45 smartin [Setting the word size] 2017/06/11 17:42 smartin 2017/06/11 17:32 smartin [Numbers in other bases] 2017/06/11 17:24 smartin [Exact versus Approximate] 2017/06/11 17:23 smartin 2017/06/11 17:02 smartin created Line 1: Line 1: - ===== Numbers ===== + ===== Basic numbers ===== - A number in newRPL is represented as exact or approximate.  To enter a number as approximate use a trailing dot.  To enter a number as exact omit any trailing dot.  For routine arithmetic this distinction doesn't matter much, but it does come into play when evaluating symbolic expressions. + ==== Approximate versus Exact ==== + + A number in **newRPL** is represented as exact or approximate.  To enter a number as approximate use a trailing dot.  To enter a number as exact omit any trailing dot.  For routine arithmetic this distinction doesn't matter much, but it does come into play when evaluating symbolic expressions. Here are some examples: Here are some examples: - | **Approximate Numbers** | **Exact Numbers** | + ^ Approximate Numbers ^ Exact Numbers ^ - | 1. | 1 | + | ''1.'' | ''1'' | - | 1.007. | 1.007 | + | ''1.007.'' | ''1.007'' | - | 1.007.e-10 | 1.007e-10 | + | ''1.007.e-10'' | ''1.007e-10'' | Arithmetic performed on numbers takes into account the operands (exact or approximate) and results are displayed accordingly. Arithmetic performed on numbers takes into account the operands (exact or approximate) and results are displayed accordingly. - For example, ''1 3 /'' results in ''0.333.'' (approximate), whereas ''1 2 /'' results in 0.5 (exact). + For example,  + 2:                             1 + 1:                             3 + …………………………………………………………………………………… + / +  results in ''0.333333333.'' (approximate), whereas  + 2:                             1 + 1:                             2 + …………………………………………………………………………………… + / + results in ''0.5'' (exact). + + ---- + + ==== Numbers in other bases ==== + + Numbers in different bases can be entered by preceding the value with a ''#'' and a trailing a letter to indicate the base (''b'' = binary, ''o'' = octal, ''d'' = decimal, ''h'' = hexadecimal; note that the trailing letter is case insensitive and that even if the ''#d'' syntax for decimal numbers is accepted, they are nevertheless displayed without leading ''#'' and trailing ''d''). + + A quicker method to enter these numbers consists in using the **base cycler**: simply start keying the number in the preferred base then press **RShold-3** and the number on the edit line will cycle between the different bases. + + The base cycler is smart enough to skip bases if the keyed number contains illegal digits. For example, if there's ''123'' on the edit line the base cycler will rotate between ''#123o'', ''#123h'' and ''123'', skipping an illegal ''#123b''. + + If the number is already on the stack the base cycler will display all four bases in succession, provided the number is integer. + + Another option is the BASE menu (**RS-3**): in its first page the soft key will give access to the aforementioned base cycler and four __non-programmable__ base conversion tools which act on the number on the edit line or the first level of the stack. + + Arithmetic can be done on numbers in different bases with the result displayed as the base of the first argument.  Only integer numbers in the range $-(2^{63}-1)$ to $2^{63}-1$ can be expressed in multiple bases. Numbers can be either exact or approximate; outside this range the base will be automatically switched to decimal. + + In other words, it is assumed that **non base-10 numbers are signed, 64-bits integers**. Of these 64 bits, the least significant 63 bits store the magnitude and the 64th most significant bit stores the sign (''0'' means positive, ''1'' means negative). Negative numbers are stored internally in __two's complement__ but are shown as positive numbers with a leading minus sign. + + For example: + 2:                         #125o + 1:                          #EEh + …………………………………………………………………………………… + - + yields ''-#231o''. + + Here are more examples of arithmetic operations in bases other than 10: + + + 2:                        #1101b + 1:                          #FFh + …………………………………………………………………………………… + + + yields ''#100001100b''. + + + 2:                           256 + 1:                        #FFFFh + …………………………………………………………………………………… + - + yields ''-65279''. + + + 2:                         #355o + 1:                    #11010101b + …………………………………………………………………………………… + * + yields ''#142461o''. + + + 2:                           #7h + 1:                             2 + …………………………………………………………………………………… + / + yields ''3.5''. + + + 2:                           #2h + 1:                            63 + …………………………………………………………………………………… + ^ + yields ''9.223372E18''. + + ==== Setting the word size ==== + + If there is a need to work with different word sizes **newRPL** provides a dedicated set of **bit operations**: these command always honor the selected word size //when returning the result//. + + The word size can be set using the command ''[[manual:chapter6:binary:cmd_stws|STWS]]'' (STore Word Size).  Valid ranges are 1 to 63 (not including the sign bit).  So, for example, to work with __32-bit signed numbers__, set the word size to ''31''. To view the currently set word size, use ''[[manual:chapter6:binary:cmd_rcws|RCWS]]'' (ReCall Word Size).  /Note that setting too small a word size can lead to overflow and hence unexpected results, such as this: + + + « 7 STWS + 120 4 BMUL + » + + + The result is ''-32'', not ''480'' as expected with a larger word size. + + ==== Bit operations ==== + + ^ Command ^ Purpose ^ Example ^ + | ''[[manual:chapter6:binary:cmd_badd|BADD]]'' | Add | ''#11001b #100000b [[manual:chapter6:binary:cmd_badd|BADD]]'' | + | ''[[manual:chapter6:binary:cmd_bsub|BSUB]]'' | Subtract | ''#371o #250 [[manual:chapter6:binary:cmd_bsub|BSUB]]'' | + | ''[[manual:chapter6:binary:cmd_bmul|BMUL]]'' | Multiply | ''#1A4h #7h [[manual:chapter6:binary:cmd_bmul|BMUL]]'' | + | ''[[manual:chapter6:binary:cmd_bdiv|BDIV]]'' | Divide | ''12 5 [[manual:chapter6:binary:cmd_bdiv|BDIV]]'' | + | ''[[manual:chapter6:binary:cmd_bneg|BNEG]]'' | Negate (Two's Complement) | ''#11001b [[manual:chapter6:binary:cmd_bneg|BNEG]]'' | + | ''[[manual:chapter6:binary:cmd_band|BAND]]'' | Bitwise AND | ''#1101010b #1100010b [[manual:chapter6:binary:cmd_band|BAND]]'' | + | ''[[manual:chapter6:binary:cmd_bor|BOR]]'' | Bitwise OR | ''#1101010b #1100010b [[manual:chapter6:binary:cmd_bor|BOR]]'' | + | ''[[manual:chapter6:binary:cmd_bxor|BXOR]]'' | Bitwise XOR | ''#1101010b #1100010b [[manual:chapter6:binary:cmd_bxor|BXOR]]'' | + | ''[[manual:chapter6:binary:cmd_bnot|BNOT]]'' | Bitwise NOT (One's Complement) | ''#11001b [[manual:chapter6:binary:cmd_bnot|BNOT]]'' | + | ''[[manual:chapter6:binary:cmd_blsl|BLSL]]'' | Bitwise Logical Shift Left | ''#11001b 4 [[manual:chapter6:binary:cmd_blsl|BLSL]]'' | + | ''[[manual:chapter6:binary:cmd_blsr|BLSR]]'' | Bitwise Logical Shift Right | ''#11001b 2 [[manual:chapter6:binary:cmd_blsr|BLSR]]'' | + | ''[[manual:chapter6:binary:cmd_basr|BASR]]'' | Bitwise Arithmetic Shift Right | ''#215o 2 [[manual:chapter6:binary:cmd_basr|BASR]]'' | + | ''[[manual:chapter6:binary:cmd_brl|BRL]]'' | Bitwise Rotate Left | ''#3FFh 4 [[manual:chapter6:binary:cmd_brl|BRL]]'' | + | ''[[manual:chapter6:binary:cmd_brr|BRR]]'' | Bitwise Rotate Right | ''#3FFh 1 [[manual:chapter6:binary:cmd_brr|BRR]]'' | + + ---- + + ==== Testing ==== + + Real numbers form an ordered field and its elements can be compared: **newRPL** provides a full set of arithmetic and logic operators plus some specialized ones. + + All these operators (except ''[[manual:chapter6:operators:cmd_ovr_cmp|CMP]]'') return ''1'' __if the test is true__ and ''0'' __if the test is false__. Actually any value different from ''0'' is considered __true__, but conventionally the operators return always ''1'' when the test succeeds. + + The classical **arithmetic** test operators are ''[[manual:chapter6:operators:cmd_ovr_eq|==]]'' (equality), ''[[manual:chapter6:operators:cmd_ovr_noteq|≠]]'' (not equality), ''[[manual:chapter6:operators:cmd_ovr_lt|<]]'' (less than), ''[[manual:chapter6:operators:cmd_ovr_gt|>]]'' (greater than), ''[[manual:chapter6:operators:cmd_ovr_lte|≤]]'' (less than or equal), ''[[manual:chapter6:operators:cmd_ovr_gte|≥]]'' (greater than or equal). + + + 2:                          #10h + 1:                       #10000b + …………………………………………………………………………………… + == + yields ''1''. + + + 2:                          #11o + 1:                           10. + …………………………………………………………………………………… + < + yields ''0''. + + **Logical** test operators are ''[[[manual:chapter6:operators:cmd_ovr_and|AND]]'', ''[[[manual:chapter6:operators:cmd_ovr_or|OR]]'', ''[[[manual:chapter6:operators:cmd_ovr_xor|XOR]]'' and ''[[[manual:chapter6:operators:cmd_ovr_not|NOT]]''. + + These operators must not be confused with the similar named bitwise operators ''[[manual:chapter6:binary:cmd_band|BAND]]'', ''[[manual:chapter6:binary:cmd_bor|BOR]]'', ''[[manual:chapter6:binary:cmd_bxor|BXOR]]'' and ''[[manual:chapter6:binary:cmd_bnot|BNOT]]'' described earlier: while the latter operate on a bit-by-bit basis, the logical operators consider the //truth value// of their arguments. Some examples will help to clarify: + + + 2:                        #1000b + 1:                       #11000b + …………………………………………………………………………………… + BAND + + yields ''#1000b'', but + + 2:                        #1000b + 1:                       #11000b + …………………………………………………………………………………… + AND + + yields ''1''. Similarly + + 2:                        #1000b + 1:                           #0b + …………………………………………………………………………………… + BOR + + yields ''#1000b'', but + + 2:                        #1000b + 1:                           #0b + …………………………………………………………………………………… + AND + + yields ''0''. + + Finally, **specialized** test operators perform particular tests: they are ''[[manual:chapter6:operators:cmd_ovr_cmp|CMP]]'', ''[[manual:chapter6:operators:cmd_ovr_same|SAME]]'' and ''[[manual:chapter6:operators:cmd_ovr_istrue|ISTRUE]]''. + + ''[[manual:chapter6:operators:cmd_ovr_cmp|CMP]]'' returns the ''[[manual:chapter6:arithmetic:cmd_ovr_sign|SIGN]]'' of the difference between its arguments: + + 2:                            -2 + 1:                             8 + …………………………………………………………………………………… + CMP + + yields ''-1''. - ---- + For real numbers + * ''[[manual:chapter6:operators:cmd_ovr_same|SAME]]'' and ''[[manual:chapter6:operators:cmd_ovr_eq|==]]'' are equivalent; + * ''[[manual:chapter6:operators:cmd_ovr_istrue|ISTRUE]]'' and ''« 0 [[manual:chapter6:operators:cmd_ovr_noteq|≠]] »'' are equivalent. + ---- + + ==== Special symbols ==== + Operations on real numbers aren't always defined on the whole field of real numbers: a notable example is the division, which is not defined if the divisor is ''0''. **newRPL** handles these occurrances defining two special symbols: ''∞'' (//infinity//) and ''NaN'' (//Not-a-Number//). + The ''∞'' symbol is returned when attempting, as anticipated, a division by ''0'' or when the result of a function (e.g. ''[[manual:chapter6:transcendentals:cmd_tan|TAN]]'') diverges. Albeit ''∞'' must not be considered a number, it obeys to a number of rules. The following examples assume flag [[manual:appendix:flags#flag-103|-103]] is cleared. + * ''∞'' ''[[manual:chapter6:operators:cmd_ovr_add|+]]'' or ''[[manual:chapter6:operators:cmd_ovr_sub|-]]'' a finite number yields ''∞''; + * ''∞'' ''[[manual:chapter6:operators:cmd_ovr_mul|*]]'' or ''[[manual:chapter6:operators:cmd_ovr_div|/]]'' a finite number yields ''∞''; + * the sign rule in multiplication or division applies, therefore ''-∞'' is a valid object; + * sum, multiplication or power of ''∞'' with itself yields ''∞''. + + The ''NaN'' symbol is **newRPL** way of informing the user that the attempted calculation returns an //undefined// result: typical examples include the calculation of the difference ''∞ - ∞'' or the sine of ''∞''. In general any function that includes ''NaN'' among its arguments will yield ''NaN''.
• manual/chapter3/reals.1497225773.txt.gz