hoc can be built in up to three floating-point precisions, corresponding to the C/C++ data types float, double, and long double. These are conventionally distinguished by suffixes indicating the number of bits in the floating-point system: hoc32, hoc64 (same as hoc), hoc80, and hoc128. Support for precisions other than 64-bit double is deficient, or nonexistent, in C/C++ implementations on several operating systems, so some hoc precisions may be unavailable on your system.
To avoid confusion with options, if a filename begins with a hyphen, it must be disguised by a leading absolute or relative directory path, e.g., /tmp/-foo.hoc or ./-foo.hoc.
If = is changed to :=, the assignment is permanent: name cannot then subsequently be redefined.
If = is changed to :=, the assignment is permanent: name cannot then subsequently be redefined.
Since command shells on some operating systems interpret quotation marks, it is usually necessary to protect them. On UNIX-like systems, use '-Dname="string' or if the value contains no characters that are significant to the command shell, -Dname=\"string\
If = is changed to :=, the assignment is permanent: name cannot then subsequently be redefined.
This option can also be set via the hoc system variable __BANNER__, but it must be set in an initialization file before code in that file to print the welcome banner is reached.
This option is a security feature: it takes effect only after all initialization files have been processed.
This option is a security feature: it takes effect only after all initialization files have been processed.
This option is a security feature: it takes effect only after all initialization files have been processed.
On some systems, it may be necessary to use this option when hoc is used in international mode (see the INTERNATIONALIZATION section below) in order to get accented letters displayed properly.
This option is a security feature: it takes effect only after all initialization files have been processed.
The hoc system variable __VERBOSE__ can also be set to zero at run time to turn off prompts; setting it to nonzero turns them back on.
The hoc system variable __PROMPT__ contains the prompt string: it can be redefined at any time.
hoc recognizes the three popular line-ending conventions in text files: line feed (LF) (UNIX), carriage return (CR) (Apple MacOS), and CR LF (PC DOS, Microsoft Windows, and several older systems). It also ignores one or more Ctl-Z characters at end of file, a horrid relic of some legacy desktop operating systems. Thus, its input files should not even require line-terminator translation when they are moved between systems.
To get a flavor of what typical hoc code looks like, visit the *.hoc and *.rc files in the hoc installation directory tree: see the INITIALIZATION FILES section below for their location.
The named files are read and interpreted in order. If no file is given or if file is -, hoc interprets the standard input.
See the INPUT FILE SEARCH PATH section below for details on how hoc finds input files.
hoc input consists of expressions and statements. Expressions are evaluated and their results printed. Statements, typically assignments and function or procedure definitions, produce no output unless they explicitly call print.
The character used to request completion can be changed: see the INITIALIZATION FILES section below.hoc> c<ESCape> cbrt ceil copysign cos cosd cosh hoc> co<ESCape> copysign cos cosd cosh hoc> cop<ESCape> hoc> copysign
In the default mode, C-p (hold the Control key down while typing p) moves up in the history list, C-n moves down, C-b moves backward in the current line, C-f moves forward, C-d deletes forward, DELete deletes backward, C-a moves to the beginning of the line, C-e moves to the end of the line, C-l repaints the screen, reprinting the current line at the top, and RETurn resubmits the line for execution.
For more details, consult the GNU Readline Library manual, available online in the info system. In emacs(1); type C-h i mreadline to get there.
On systems with IEEE 754 arithmetic, such numbers are capable of representing integers of up to 53 bits exactly, excluding the sign bit. This is an integer range of -(2^53) ... 2^53, or -9,007,199,254,740,992 ... 9,007,199,254,740,992.
Some systems may have hoc variants named hoc32, hoc64, hoc80, or hoc128, in which case, hoc's default precision is indicated by the program name: 32-bit, 64-bit, 80-bit, or 128-bit. hoc and hoc64 are identical on all systems with IEEE 754 arithmetic.
For hoc32, on systems with IEEE 754 arithmetic, numbers are capable of representing integers up to 24 bits exactly, excluding the sign bit. This is an integer range of -(2^24) ... 2^24, or -16,777,216 ... +16,777,216.
For hoc80, on systems with IEEE 754 arithmetic, numbers are capable of representing integers up to 64 bits exactly, excluding the sign bit. This is an integer range of -(2^64) ... 2^64, or -18,446,744,073,709,551,616 ... +18,446,744,073,709,551,616.
For hoc128, on systems with IEEE 754 arithmetic, numbers are capable of representing integers up to 112 bits exactly, excluding the sign bit. This is an integer range of -(2^112) ... 2^112, or -5,192,296,858,534,827,628,530,496,329,220,096 ... +5,192,296,858,534,827,628,530,496,329,220,096.
Numbers may be signed, and may optionally contain a decimal point, a power-of-ten exponent, and a precision suffix. The exponent consists of an exponent letter, one of d, D, e, E, q, or Q (supported by one or more of Ada, C, C++, Fortran, Java, and Pascal), followed by an optionally-signed integer. The precision suffix (used by C, C++, and Java) is one of f, F, l, or L. The suffix does not affect the precision of the constant for hoc: it is recognized only to simplify incorporation into hoc programs of numbers from programs in other languages, and their output.
A hexadecimal floating-point number format, introduced in the latest ISO C Standard, ISO/IEC 9899:1999 (E) Programming languages --- C, usually known by its short name, C99, is also supported, and implemented by portable private code in hoc. This format consists of an optional sign, then 0x or 0X, followed by one or more hexadecimal digits (0\(mi9 A\(miF a\(mif) containing at most one hexadecimal point, optionally followed by a binary (power-of-two) exponent consisting of p or P followed by an optionally-signed decimal integer. If present, the exponent may optionally be followed by a precision suffix letter: one of f, F, l, or L. Thus, -0x1.00000p8, -0x100, -0x100000p-12f, -0x10p+4L, -0x1p+8, -0x1p00008, and -0x1p8 all represent the decimal number -256.
The hexadecimal format, while awkward for humans, has the advantage of guaranteeing exact input/output conversions on all platforms, and hoc consequently uses this format in files created by the save() command.
All characters in 1 ... 255 are representable in strings; as in C and C++, character 0 (ASCII NUL) is reserved as a string terminator.
In string constants, nonprintable characters may be represented by the usual escape sequences defined in Standard C and Standard C++, plus one extension (\E):
Backslash followed by any other character than those listed is simply discarded: \W reduces to W.
- \
- backslash: ASCII decimal 92.
- \"
- quotation mark: ASCII decimal 34.
- \a
- alert or bell (ASCII BEL: decimal 7).
- \b
- backspace (ASCII BS: decimal 8).
- \E
- escape (ASCII ESC: decimal 27).
- \f
- formfeed (ASCII FF or NP: decimal 12).
- \n
- newline (ASCII LF or NL: decimal 10).
- \r
- carriage return (ASCII CR: decimal 13).
- \t
- horizontal tab (ASCII HT: decimal 9).
- \v
- vertical tab (ASCII VT: decimal 11).
- \o \oo \ooo
- octal character number (o = 0\(mi7) in one to three digits.
- \xh...
- hexadecimal character (h = 0\(mi9A\(miF or 0\(mi9a\(mif) in one or more digits.
Underscore (_) by itself is a reserved variable containing the value of the last numeric expression evaluated. Double underscore (__) is a reserved variable containing the value of the last string expression evaluated. They cannot be assigned to by user code.
- CATALAN
- Catalan's constant: sum((-1)^i/(2*i+1)^2, i = 0..infinity) =
approximately 0.915965594177219015054603514932...- CLASS_xxx
- One of eleven possible return values from the class(x) function; see the section DESCRIPTIONS OF BUILT-IN FUNCTIONS AND PROCEDURES below for details.
- DEG
- 180/PI, degrees per radian
- E
- base of natural logarithms
- GAMMA
- Euler's constant:
limit(sum(1/i,i=1...n) \(mi ln(n), n \(-> infinity) = approximately 0.577215664901532860606512090082...- INF or Inf or Infinity
- IEEE-754 floating-point infinity
- MAXNORMAL
- Largest finite normalized floating-point number.
- MINNORMAL
- Smallest (in absolute value) nonzero normalized floating-point number.
- MINSUBNORMAL
- Smallest (in absolute value) subnormal floating-point number. If your computer system does not support subnormal numbers, this is identical to MINNORMAL.
- NAN or NaN
- IEEE-754 floating-point not-a-number
- PHI
- golden ratio:
(1 + sqrt(5))/2 =
approximately 1.61803398874989484820458683436...- PI
- ratio of the circumference of a circle to its diameter, approximately 3.14159265358979323846264338327...
- PREC
- maximum number of significant digits in output, initially 17 on most systems (the precise value is computed dynamically, from Matula's 1968 result: ceil(N/log_b(10) + 1), for a host floating-point system with N base-b digits). PREC = 0 gives shortest `exact' values.
- QNAN or QNaN
- IEEE-754 floating-point quiet not-a-number
- SNAN or SNaN
- IEEE-754 floating-point signaling not-a-number
More information on the floating-point constants is available in the FLOATING-POINT ARITHMETIC section below.
- _
- [immutable number] Value of the last numeric expression printed (initialized to 0.0 on startup).
- __
- [immutable string] Value of the last string expression printed (initialized to an empty string on startup).
- __BANNER__
- [reassignable number] Nonzero (true) if printing of welcome banners is permitted. It can be changed by the -no-banner option.
- __CPU_LIMIT__
- [immutable number] Current limit on CPU use, in seconds. It is normally infinite, but can be reset by the cpulimit() function.
- __DATE__
- [constant string] Date of the start of job execution, in the form "Dec 16 2001". The day number has a leading space if only one digit is needed, so that the string always has constant width.
- __FILE__
- [constant string] Name of the current input file. This is "/dev/stdin" when hoc is reading from the standard input.
- __FILE__[n]
- [constant string] Name of the n-th input file in the current job. This provides a history of exactly what files have been read. Because hoc does not yet support arrays, the only way to display these is with the who() function.
- __GID__
- [constant number] Group numeric identifier code.
On operating systems that do not support the concept of group and user identifiers, it is set to zero.
- __HOCRC__
- [constant string] Pathless filename of the optional hoc user startup file; it is stored in the user's home directory.
- __IEEE_754__
- [constant number] Nonzero (true) if the host system supports IEEE 754 arithmetic.
- __LINE__
- [constant number] Number of the current input line in the file named by __FILE__.
- __MAX_xxx__
- [immutable number] One of several numeric constants that report current sizes of internal storage areas in hoc that grow as needed. See the IMPLEMENTATION LIMITS section below for details.
- __PACKAGE_BUGREPORT__
- [constant string] Where to report bugs.
- __PACKAGE_DATE__
- [constant string] Date of last modification of the software.
- __PACKAGE_NAME__
- [constant string] Program name.
- __PACKAGE_STRING__
- [constant string] Program name and version number.
- __PACKAGE_VERSION__
- [constant string] Program version number.
- __PID__
- [constant number] Numeric process identifier.
On operating systems that do not support such a concept, it is set to zero.
- __PROMPT__
- [reassignable string] Current prompt string. Prompting is controlled by the setting of __VERBOSE__ (see below).
For example,
__PROMPT__ = "\n\E[7mInput:\E[0m "will produce a blank line followed by a prompt in inverse video in terminal emulators, such as xterm(1) and DEC VT100, that follow the ANSI X3.64-1979 or ISO 6429-1983 terminal standards.
If __PROMPT__ contains the two-character format string %d, that string will be replaced by the prompt count: for example, this silly setting
__PROMPT__="\E[4;5;34;43m[%d]\E[0m: "will display the count digits in blue, and underlined, on a yellow background, in an xterm(1) window that supports text color attributes. [Run dircolors -p for more information on color settings.]
- __READLINE__
- [constant number] Nonzero (true) if the GNU readline library is in use.
- __SYSHOCDIR__
- [constant string] Name of the installation directory in which hoc startup files are stored.
- __SYSHOCHLPBASE__
- [constant string] Pathless filename of the top-level startup help file.
- __SYSHOCHLP__
- [constant string] Full filename of the top-level startup help file.
- __SYSHOCPATH__
- [constant string] System directory search path that is substituted for an empty component in the HOCPATH environment variable input file directory search list.
- __SYSHOCRCBASE__
- [constant string] Pathless filename of the top-level startup help file.
- __SYSHOCRC__
- [constant string] Full filename of the top-level startup file.
- __SYSHOCXLTBASE__
- [constant string] Pathless filename of the top-level translation file.
- __SYSHOCXLT__
- [constant string] Full filename of the top-level translation file.
- __TIME__
- [constant string] Local time-of-day (24-hour clock) of the start of job execution, in the usual hours, minutes, seconds form "14:57:23".
- __UID__
- [constant number] User numeric identifier code.
On operating systems that do not support the concept of group and user identifiers, it is set to zero.
- __VERBOSE__
- [reassignable number] Nonzero (true) if hoc should prompt for input from interactive files. The actual prompt string is controlled by the __PROMPT__ variable.
[NB: A bug in the GNU readline library (version 4.2a) makes this variable ineffective; it works correctly with the -no-readline option. The bug has been reported to the readline maintainers.]
- ^
- Exponentiation.
- ! - ++ --
- Logical negation, arithmetic negation, increment-by-one, decrement-by-one. As in C and C++, the latter two may be applied before a variable (acting first before taking the value), or after (taking the current value first, then acting).
- * / %
- Multiply, divide, modulus.
- + -
- Add, subtract.
- > >= < <= <> == !=
- Greater than, greater than or equal to, less than, less than or equal to, less than or greater than, equal to, not equal to.
The <> operator is not the same as !=; they differ when one of the operands is a NaN. Since NaNs are unordered, NaN <> NaN is 0 (false), while NaN != NaN is 1 (true).
- &&
- Logical and. Both operands are always evaluated, unlike in C and C++, where the second is evaluated only if the first is nonzero (true).
- ||
- Logical or. Both operands are always evaluated, unlike in C and C++, where the second is evaluated only if the first is zero (false).
- = += -= *= /= %= :=
- Assignment, assign the left-hand side the (sum, difference, product, dividend, or modulus) of its current value and the right-hand side, permanent assignment. The operator := is a one-time-only assignment operator, used for defining permanent constants that cannot be redefined in the same hoc session.
As in C and C++, assignment is a right-associative expression whose value is the left-hand side. This means that x = y = z = 3 is interpreted as x = (y = (z = 3)). That is, 3 is assigned to z, then that result is assigned to y, and finally, that result is assigned to x, so all three variables are assigned the value 3. Similarly, sqrt(x = 4) assigns the value 4 to x before computing and returning its square root.
Expression lists in print-like statements, and in argument lists, are evaluated in strict left-to-right order. Thus, the output of expressions with side effects, such as
is predictable: that example printsn = 3 print ++n, n++
4 4
Numbers in string expressions are converted to strings according to the current precision variable, PREC.s = "hello" ", " "wor" "ld" s = "hello, world"
Several string functions listed below augment string expressions.k = 123 PREC = 4 s = "abc" k "def" PI println s abc123def3.142
These numeric built-in functions take zero arguments: rand, second, snan, and systime.
These numeric built-in functions take one numeric argument: abs, acos, acosh, asin, asinh, atan, atanh, cbrt, ceil, cos, cosd, cosh, double, erf, erfc, exp, expm1, exponent, factorial, floor, gamma, ilogb, int, isfinite, isinf, isnan, isnormal, isqnan, issnan, issubnormal, J0, J1, lgamma, ln, log, log10, log1p, log2, macheps, nint, number, randl, rint, rsqrt, setrand, significand, sin, sind, single, sinh, sqrt, tan, tand, tanh, trunc, Y0, and Y1.
These numeric built-in functions take two numeric arguments: copysign, errbits, fmod, gcd, hypot, Jn, lcm, ldexp, logb, max, min, randint, nearest, nextafter, remainder, scalb, and Yn.
These string built-in functions take zero arguments: logoff, logon, now, and pwd.
These string built-in functions take one argument: cd, char, eval, ftoh, getenv, length, hexfp, hexint, htof, ichar, load, logfile, msg_translate, printenv, protect, set_locale, string, tolower, toupper, and who.
These string built-in functions take two arguments: index, putenv, save, and strftime.
This string built-in function takes three arguments: substr.
These numeric functions take one symbol argument: defined and delete.
These symbol functions take one string argument: symnum and symstr.
These startup file procedures take no arguments: author, dirs, help, help_xxx, news popd, and xd.
The help system (described later) documents each of these functions, and any additional ones provided by startup files. Most have the same names as they do in C, C++, and Fortran, so many will already be familiar to users who have learned any of those programming languages.
Built-in functions and procedures are immutable: they cannot be redefined by the user in hoc code. User-defined variables, functions, and procedures can be redefined at any time to objects of the same type. Variables can be redefined to be functions or procedures. However, the reverse does not hold: once a name has been used as a function or procedure, it can only be redefined to be a new function or procedure.
The procedure abort(message) prints message, immediately terminates evaluation, and returns to the top-level interpreter, discarding and clearing the function/procedure call stack. It is equivalent to a similar internal function that hoc uses to recover from catastrophic errors. Use it sparingly!
The function read(x) reads a value into the variable x. The value must be either a number, or a quoted string, or an existing variable or named constant. The return value is 1 on success, or 0 on end-of-file; the function aborts for any other error condition.
The function who(pattern) produces a lengthy report of all of the named constants and variables with their current values, plus the names of all built-in functions and procedures, and all user-defined functions and procedures. Only those names which match the argument string, pattern, are included.
To print all symbols, use who("*"). The return value is always an empty string.
Symbols with three or more leading underscores are for internal use by hoc, and are thus considered hidden. They can only be shown by a suitable pattern argument to who(). Hidden symbols are used for locale translations of embedded strings. See the INTERNATIONALIZATION section below for further details.
The break statement exits from the body of a for or while loop, skipping evaluation of any post-body for-loop expression. Execution resumes with the statement that follows the loop body.
The continue statement exits from the current iteration of the body of a for or while loop. Execution resumes with evaluation of any post-body for-loop expression, and the conditional test that governs execution of the next iteration.
break and continue are illegal outside loop bodies.
Newline or semicolon ends a statement. Backslash-newline is equivalent to a space.
Functions and procedures are introduced by the words func and proc, followed by the function/procedure name, a parenthesized list of arguments, and the function/procedure body, which may be either a single statement, or a braced statement group.
The return statement is used to return a value from a function.
Variables inside the body are local by default: they are known only within the body, even if they have the same names as variables elsewhere.
Variables listed in a global statement are visible outside the body.
Arguments are passed by value, so it is impossible for the body to modify their values in the caller.
Here is an example to demonstrate these features:
proc show(x) \
{
global last_x, last_xsq
println x
last_x = x
last_xsq = x^2
y = x
x = 999999999
}
x = 5
show(x)
5
last_x
5
last_xsq
25
y
0
x
5
Built-in named constants are always globally
visible, and thus need not be listed in a
global
statement; however, some people prefer to do so as
a matter of documentation.
A global statement may appear outside a function/procedure body, but does nothing useful.
Inside a function/procedure body, a global statement affects only variables that follow it, so it should generally occur at the start. Here is what happens if you do not follow that recommendation:
y = 3
proc foo() \
{
for (k = 1; k < 3; ++k) \
{
println y
global y
println y
}
}
foo()
0
3
0
3
The first reference to y is to an
uninitialized, and therefore zero by default,
variable. The second one is to the global value.
This behavior is a feature, not a bug, but you
probably should not exploit it!
In older versions of hoc, function/procedure statement argument lists were empty, and within the body, numeric arguments were referred to as $1, $2, etc., and string arguments as $$1, $$2, etc., and all other variables were global. This practice is now deprecated, though still recognized, and the default visibility has changed from global to local.
The statement print prints a list of expressions that may include string constants such as "hello\n". It does not print a final newline: the last expression must end with one if a newline is required.
The statement println works like print, but always supplies a following newline.
The list items printed by print and println are separated by the current value of __OFS__ (output field separator), normally a single space.
The printf statement is similar to print, but its initial argument must be a format string conforming to a large subset of the syntax supported by Standard C's printf(1) statement. List item separation is controlled entirely by the format; __OFS__ is not used. Data type length modifiers (h, l, ll, L) are not permitted, nor are n (dynamic field width) or p (pointer) format descriptors. Otherwise, the % (literal percent), c (character), d (decimal integer), E (uppercase exponential floating-point), e (lowercase exponential floating-point), f (fixed decimal), G (uppercase generalized floating-point), g (lowercase generalized floating-point), i (decimal integer), o (octal integer), s (string), u (unsigned integer), x (lowercase hexadecimal integer), and X (uppercase hexadecimal integer) format descriptors, with optional sign, field-width, and number-of-digits modifiers are recognized. In brief, each format descriptor is required to match this regular expression: %(%|[-+0 ]?[0-9]*([.][0-9]*)?[cdeEfgGiosuxX])" .
The sprintf statement is similar to printf except that its result is returned as a string value, instead of being printed.
For user convenience, and portability across file systems, an empty component in the directory path list stands for a default system path that includes several directories where other hoc are installed. Thus, hoc assumes a default HOCPATH value, if one is not already defined, of .:, meaning the current directory, followed by the default system path.
As a further user convenience, if an attempt to open a file fails, and the filename does not end in .hoc, the open is retried with that ending, allowing omission of hoc's recommended file extension.
On most modern systems, this arithmetic conforms closely (or loosely) to the 1985 IEEE 754 Standard for Binary Floating-Point Arithmetic. This arithmetic system has numerous advantages over older designs, and has helped enormously to improve the environment for, and portability and reliability of, numerical software.
Biased, rather than explicitly signed, exponents are conventional in floating-point architectures. For IEEE 754 64-bit arithmetic, the exponent bias is 1023; that is, the true exponent is 1023 less than the stored biased value.
The smallest biased exponent (0), and the largest biased exponent (2^11 - 1 = 2047), are given special interpretation, described below for subnormals, and Infinity and NaN, respectively.
func hassubnormals() \
return (issubnormal(1/(((1 - 2^(-53)) * 2^1023) * 2)))
With a predefined constant, this can also be
written as
func hassubnormals() return (issubnormal(1/MAXNORMAL))
In IEEE 754 arithmetic, macheps(1) is about 2.22e-16, or more precisely, 2^(-52). The negative of its base-10 logarithm is the number of decimal digits that can be represented. An error of macheps(x) is called an ULP (Unit in the Last Place). If y is an approximation to x, then with the definition
func errbits(x,y) \
{
if (x == y) \
return (0) \
else \
return (ceil(log2(abs((x - y)/max(x,y))/macheps(x))))
}
errbits(x,y)
is the number of bits that are in error in
y:
that is, the base-2 logarithm of the relative
error in ULPs, rounded up to the nearest integer.
Incidentally, this function behaves as expected if
either of its arguments are NaN (described below),
or Infinity of opposite signs, even though there
are no tests for those values: the result is a
NaN.
One might reasonably argue for errbits(x,y) that the case of two Infinity arguments of like sign should also return a NaN. The current implementation does not include such a test, but doing so would require just one additional statement: if (isinf(x) && isinf(y)) return (NAN).
macheps(0) is the smallest representable floating-point number, either normalized, or subnormal if supported. Thus, the test function above can be written more simply and portably (since it also works for non-IEEE 754 systems) as
but it will run somewhat more slowly, since the current portable implementation of macheps(x) involves a loop. Another simple implementation of this function uses predefined constants:func hassubnormals() return issubnormal(macheps(0))
func hassubnormals() return (MINNORMAL > MINSUBNORMAL)
Both Infinity and NaN are signed, but the sign of a NaN is usually irrelevant, and may not reflect how it was computed: some architectures only generate negative NaNs, others generate only positive ones, and a few may preserve the expected sign in the NaN produced.
hoc considers the native NaN to be positive, even if its binary encoding has a negative sign. Thus, copysign(1.0,NaN) returns 1.0, and copysign(1.0,-NaN) returns -1.0 on all systems where NaNs are available.
Negative zero is generated from, e.g.,
0 / -Infinity sqrt(-0)
In principle, you should be able to get a negative zero in any programming language by simply writing -0, but many compilers will convert this to positive zero. You then have to introduce a variable, assign it a zero, and negate the variable, possibly hiding the negation in an external function that simply returns its value, to foil optimizers.
In hoc, however, -0 always works correctly.
The result will be either +1 or -1.copysign(1,x)
On these older systems, hoc tries to prevent generation of exceptional values that might otherwise terminate the job: it aborts such computations with an error message, and returns you to top level, ready for more input. On IEEE 754 systems, computation in hoc simply proceeds as the Standard intended.
The IEEE 754 nonstop property is exceedingly important in modern heavily-pipelined, or parallel, or superscalar, or vector, architectures, all of which have multiple operations underway at once. An interrupt to handle a floating-point exception in software is extremely costly in performance.
Infinity behaves somewhat like a mathematical infinity:
finite / Infinity \(-> 0 Infinity * Infinity \(-> Infinity Infinity^(finite or Infinity) \(-> Infinity
NaN is produced whenever one or more operands of an arithmetic expression is a NaN, or from most numerical functions with NaN arguments, or from expressions where a limiting value cannot be determined:
Infinity \(mi Infinity \(-> NaN Infinity / Infinity \(-> NaN 0 / 0 \(-> NaN
NaN has a unique property not shared by any other floating-point values, including Infinity: it is not equal to anything, even itself! This should be usable as a completely portable test for a NaN, even on older systems that do not have IEEE 754 arithmetic:
(x != x) is true if, and only if, x is a NaN.
Regrettably, compiler writers on several systems have failed to grasp this important point, and they incorrectly optimize this test to false. Thus, portable code needs to use a test function, and hoc provides three of them: isnan(x), isqnan(x), and issnan(x), which return true if x is a NaN (of any flavor, or quiet, or signaling, respectively).
if (x > y) \
print "x is greater than y\n" \
else \
print "x is less than or equal to y\n"
you should instead write
if (isnan(x)) \
print "x is a NaN\n" \
else if (isnan(y)) \
print "y is a NaN\n" \
else if (x > y) \
print "x is greater than y\n" \
else \
print "x is less than or equal to y\n"
Since if \(mi else statements are very common in software, but most programmers, and computer textbook authors, are not sufficiently familiar with IEEE 754 arithmetic, you should expect that most existing software, and textbook examples, will fail to behave consistently, or correctly, when dealing with NaN, and possibly also Infinity.
There have been some major disasters, such as the failure of the Ariane satellite launch in West Africa, the failure of Patriot missiles in the Gulf War, and a U.S. nuclear aircraft carrier sitting dead in the water for six hours, all attributed to computer programmers who lacked sufficiently understanding of computer arithmetic. Arithmetic really does matter!
Numerical software often contains convergence tests of the form
while (tolerance is not reached)
reduce the tolerance
If a NaN ever appears in the
while
expression, the test will never be satisfied, and
the program will be in an infinite loop. Even
famous libraries like EISPACK and LINPACK have
routines that will never return because of loops
caused by NaNs. [In fairness, both of those
libraries were developed before IEEE 754
arithmetic existed, but CDC and Cray machines of
that era had special values similar to Infinity
and NaN, so even then, there were systems where
the code could endlessly loop.]
Vendor-provided floating-point systems and run-time libraries are not always entirely reliable in their handling of signed zero, Infinity, and NaN, and portable programs like hoc can help to ferret out implementation differences, and errors that should be reported to the vendors. As noted earlier, signed zero is often botched by compiler writers, and two functions commonly available in most programming languages, max(x,y) and min(x,y), in particular are badly done. Their simple implementations use a two-branch conditional like this one for max(x,y): if (x > y) return x else return y. If either argument is a NaN, then the test will fail, and the second argument will be returned, leading to inconsistent nonsense like max(1,NaN) \(-> NaN but max(NaN,1) \(-> 1. The C and C++ languages lack such functions (users are expected to write them as macros), but Fortran and many other languages have them. In the fall of 2001, tests of 61 Fortran compilers on 15 different UNIX platforms showed that all fail to behave consistently for max(x,y) and min(x,y).
- (1)
- access to floating-point status flags, so that you can tell after the fact whether a computation encountered any exceptional conditions, and
- (2)
- access to rounding control, which determines whether rounding is to minus Infinity, zero, nearest, or plus Infinity. The default is always round-to-nearest.
Once rounding control is available, hoc could, in principle, be extended to support interval arithmetic, in which each numeric operation produces upper and lower bounds for the result. Of course, a proper implementation would also require such support in all of the mathematical functions in the C/C++ run-time library, and such support is lacking almost everywhere.
Users are encouraged to follow these help convention with their own hoc code.
The entire help corpus is intentionally external to hoc itself, to facilitate modification, partial replacement, and internationalization, as discussed in the next section.
Changing the language alters only documentation and program messages: the basic hoc language remains unchanged, and English-centric, just as do virtually all computer programming languages.
You could thus launch a German version of hoc like this:locale -a | sort -f
Environment variables, rather than command-line options, control the locale selection, because it is likely that most individuals will want to choose a fixed locale, and that can be done once and for all in user login files, and also because several UNIX library functions access the locale environment variables to guide their behavior. UNIX users could also create convenient shell aliases, e.g., in csh(1)/ tcsh(1) syntax,env LANG=de hoc
alias hoc-da 'env LANG=da hoc \!*' alias hoc-de 'env LANG=de hoc \!*' alias hoc-fr 'env LANG=fr hoc \!*' ...
Locale support is usually present in one of these directories; besides using the locale(1) command as shown in the previous subsection, you can run ls(1) on the appropriate one of them to see what locales are installed on your system:
- /usr/share/locale
- Apple Darwin (MacOS X), FreeBSD, GNU/Linux (all architectures)
- /usr/lib/nls/loc
- Compaq/DEC Alpha, IBM AIX
- /usr/share/i18n/locales
- GNU/Linux (all architectures)
- /usr/lib/nls/loc/locales
- Hewlett-Packard HP-UX
- /usr/lib/locale
- SGI IRIX, Sun Solaris
# Show time in the default locale:
hoc> strftime("%c",systime())
Fri Dec 21 15:18:14 2001
# Switch to Portuguese: ISO8859-1 (Latin-1) encoding:
hoc> old_lc_time = putenv("LC_TIME", "pt")
hoc> strftime("%c",systime())
sex 21 dez 2001 03:17:29 PM MST
# Restore the original locale:
hoc> ignore = putenv("LC_TIME", old_lc_time)
The current locale setting can be saved and
restored as shown. Less desirably, the value
"C" resets it to the C/C++ default of
English.
The locale code is interpreted as the name of a subdirectory in which to find a localized version of any system file that hoc loads at startup time. For example, in a Danish locale, it will load the English file, help.hoc, and then the Danish file, da/help.hoc, from the hoc system installation directory, provided that the localized file exists. Otherwise, hoc is silent about its absence.
These variables are normally only set in the translations.hoc files in the hoc system directory tree, but they can also be set by user programs as well, unless they have been defined as permanent constants.
See the comments in those files for further documentation. Except for translation work, it should never be necessary for ordinary users to reference or modify these variables.
xterm -fn \
-adobe-courier-medium-r-normal--14-100-100-100-m-90-iso8859-1 &
to get a 14pt font with all of the characters
needed for ISO8859-1 (Latin 1, handling most of
the languages of Western Europe, and many others,
such as Hawaiian, Indonesian, and Swahili).
Your system manager may be able to tell you about additional window system fonts that may also be available, but are not loaded by default. For example, at the maintainer's site, there is a large collection of Asian and European fonts installed in the emacs(1) editor tree. To add, say, the European collection, in a shell window type
The new fonts will then be available, and will be listable by xlsfonts(1). You can make those additions permanent by adding those two commands to your $HOME/.xinitrc or $HOME/.xsession file; the name is platform-dependent, so the best choice is to make them identical, with one a symbolic link to the other.xset fp+ /usr/local/share/emacs/fonts/European xset fp rehash
Use
to find out what font directories are currently in the font search path.xset q
Each X Window System font directory has a fonts.dir text file that maps short file names to long font names. There is sometimes also a fonts.alias text file to provide short aliases for the otherwise rather long font names used in the X Window System. You can scan those files to see what is available.
Recent versions of xterm(1) have a special option, -u8, to handle UTF-8 multibyte encoding, but you then need to use a font with the corresponding character repertoire:
xterm -u8 -fn \
-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1 &
% env LANG=fr hoc -------------------------------------------------------------- Welcome to the extensible high-order calculator, hoc. This is hoc version 7.0.0.beta [15-Dec-2001]. Type help() for help, news() for news, and author() for author information. This system supports IEEE 754 floating-point arithmetic. -------------------------------------------------------------- -------------------------------------------------------------- Bienvenue �� la calculatrice, hoc. C'est la version 7.0 du 15 d��cembre 2001. Taper aide() pour de l'assistance, nouvelles() pour des nouvelles, et auteur() pour des renseignements sur les auteurs. Cet ordinateur supporte l'arithm��tique en virgule flottante du standard IEEE 754. --------------------------------------------------------------
The maintainer will be grateful for contributions of additional translations of hoc help files and internal messages!
By suitable manual edits to the site-init.el file in that directory, your system manager could make hoc-mode support automatically available, but the hoc installation process cannot safely do that automatically.
You can test whether this has been done at your site by visiting a new file with extension .hoc; if the emacs(1) mode line shows (hoc ...), instead of something else, like (fundamental ...), then you need do nothing more: hoc-mode is already fully installed.
Otherwise, in order to avoid the need for tedious manual loading of the hoc support in emacs(1), add this snippet of Emacs Lisp code at the end of your $HOME/.emacs initialization file:
(if (string-lessp (substring emacs-version 0 2) "19") ; earlier than 19.x
(progn
(setq auto-mode-alist
(cons (cons "\.hoc$" 'hoc-mode) auto-mode-alist))
(autoload 'hoc-mode "hoc"
"Enter hoc mode." t nil))
(progn
(if (not (assoc "\.hoc$" auto-mode-alist))
(setq auto-mode-alist
(cons (cons "\.hoc$" 'hoc-mode) auto-mode-alist)))
(autoload 'hoc-mode "hoc"
"Enter hoc (high-order calculator) mode." t nil)))
There are two sections in this code, one for (now
very old)
emacs(1)
versions before 19.x, and the other for all newer
versions. They add a binding between files with
extension
.hoc
and
hoc-mode
in
emacs(1),
and arrange for the
hoc.el
library to be loaded the first time that it is
required.
Two additional functions are provided to ease the task of creating help procedures: hoc-printify and hoc-unprintify. Both operate on the region, converting text to print statements, or the reverse.
In the following descriptions, square brackets on number ranges indicate that the endpoint is included; parentheses indicate that the endpoint is excluded.
See also help_dirs(), help_popd(), help_pushd(), help_pwd(), and help_xd().
hoc strings are internally terminated by a NUL character, so char(0) is equivalent to an empty string, "", and ("X" char(0) "Y") evaluates to ("X" "" "Y") which in turn reduces to "XY".
- CLASS_NEGINF
- negative infinity
- CLASS_NEGNORMAL
- negative normal
- CLASS_NEGSUBNORMAL
- negative subnormal
- CLASS_NEGZERO
- negative zero
- CLASS_POSINF
- positive infinity
- CLASS_POSNORMAL
- positive normal
- CLASS_POSSUBNORMAL
- positive subnormal
- CLASS_POSZERO
- positive zero
- CLASS_QNAN
- quiet NaN
- CLASS_SNAN
- signaling NaN
An eleventh value is reserved to flag classification failure:
- CLASS_UNKNOWN
- should never happen
If the limit is exceeded, execution of the current expression is aborted, control returns to the top-level interpreter, and the time limit is incremented by the current value of __CPU_LIMIT__.
Although t may be fractional, on most operating systems, the time limit is an integer, so t will be rounded up internally to the nearest integer before setting the time limit.
If resource usage and limits are not supported on the current platform, this function has no effect, other than setting __CPU_LIMIT__, and returning Infinity.
By default, there is no time limit for the job (although some operating systems may impose such limits).
Negative, zero, and NaN arguments are treated like Infinity.
NB: This function is experimental, and may be withdrawn in future versions.
Programming note: This function can be used in hoc libraries to provide default values of variables, for example,
if (!defined(seed)) seed = 123456789
Most user-defined symbols can be deleted, but hoc kernel symbols, and user-defined immutable symbols, cannot.
See also help_cd(), help_popd(), help_pushd(), help_pwd(), and help_xd().
This function makes it possible for hoc programs to construct new hoc code on-the-fly and then run it.
For small x, exp(x) is approximately 1, so there is serious subtraction loss in directly using exp(x) \(mi 1; expm1(x) avoids this loss.
From Sun Solaris documentation: ``The expm1() and log1p() functions are useful for financial calculations of ((1 + x)^n \(mi 1) / x, namely:
expm1(n * log1p(x))/x
when x is very small (for example, when performing calculations with a small daily interest rate). These functions also simplify writing accurate inverse hyperbolic functions.''
x == significand(x) * 2^exponent(x)
where |significand(x)| is in [1...2).
For IEEE 754 arithmetic, normal numbers have exponent(x) in [-1022...1023] and subnormal numbers, if supported, have exponent(x) in [-1074...1023].
WARNING: The power 2^exponent(x) will underflow to zero for IEEE 754 subnormal numbers, so for such numbers, the right-hand side must be computed with suitable scaling, like this:
(significand(x) * 2^(exponent(x) + 52)) * 2^(-52)
For readability, a separating underscore is inserted between groups of eight hexadecimal digits.
This function is the inverse of htof(s).
"+0x1.hhhhh...p+ddddd"
Trailing zeros in the fraction, and leading zeros in the exponent, are dropped, and the sign is always included.
See also help_hexint(), help_number(), and help_string().
"+0xhhhhh..."
Leading zeros are dropped, and the sign is always included.
If x is too big to represent as an exact integer, then the floating-point representation, hexfp(x), is returned instead.
See also help_hexfp(), help_number(), and help_string().
Nonhexadecimal digits in s are ignored.
This function is the inverse of ftoh(x).
This function has possibly unexpected behavior for exceptional arguments: when either argument is Infinity, then the result is Infinity, even if the other argument is a NaN! The explanation is found on the 4.3BSD manual page:
... programmers on machines other than a VAX (it has no infinity) might be surprised at first to discover that hypot(+infinity,NaN) = +infinity. This is intentional; it happens because hypot(infinity,v) = +infinity for all v, finite or infinite. Hence hypot(infinity,v) is independent of v. Unlike the reserved operand on a VAX, the IEEE NaN is designed to disappear when it turns out to be irrelevant, as it does in hypot(infinity,NaN). ...
On some architectures (e.g., Intel x86 and MIPS), there is only one type of NaN. isqnan(x) is then defined to return isnan(x).
On some architectures (e.g., Intel x86 and MIPS), there is only one type of NaN. issnan(x) is then defined to return isnan(x).
You can test whether your system has both quiet and signaling NaNs like this: issnan(NaN). The result is 0 (false) if distinct NaN types are available, and 1 (true) if not.
Because gamma(x) has poles at zero and at negative integer values, and grows factorially with increasing x, it reaches the floating-point overflow limit fairly quickly. For 64-bit IEEE 754 arithmetic, this happens at approximately x = 206.779. However, lgamma(x) is representable almost to the overflow limit. In 64-bit IEEE 754 arithmetic, this happens at approximately x = 2.55e+306 (the overflow limit is 1.80e+308).
Unfortunately, there is mathematically-unavoidable accuracy loss when gamma(x) is computed from exp(lgamma(x)), so you should avoid the logarithmic form unless you really need large arguments that would cause overflow.
See the INPUT FILE SEARCH PATH section below for details on how hoc finds input files.
Loaded files can themselves contain load() commands, with nesting up to some unknown limit imposed by the host operating system on the maximum number of simultaneously-open files for a process, user, or the entire system.
This command can be disabled for security reasons by the command-line -no-load or -secure options.
The return value is an empty string on success, and otherwise, an error message.
Input is recorded verbatim. Output is recorded in comments. This permits the logfile to be read by hoc later, allowing a session to be replayed.
If a logfile is already opened, it is closed before opening the new one.
Logging may be turned on and off with logon() and logoff(), and can be entirely disabled for security reasons by the command-line -no-logfile option.
The return value is an empty string on success, and otherwise, an error message.
macheps(1) is the normal machine epsilon.
macheps(-x) is macheps(x)/base, or equivalently, the smallest number that can be subtracted from x with the result still different from x.
macheps(0) is the smallest representable floating-point number. Depending on the host system, it may be a normal number, or a subnormal number (invoke help_subnormal() for details).
If either argument is a NaN, the result is a NaN.
If either argument is a NaN, the result is a NaN.
Please use this function in your own hoc code to ensure that your messages can be translated to other languages without any changes whatsoever to your code.
"Wed Jul 4 14:57:51 2001"
If the month day has only one digit, then it is
preceded by an extra space.
s should contain either a hexadecimal floating-point number, a hexadecimal integer, a decimal floating-point number, a decimal integer, or a representation of NaN or Infinity.
If s contains a number followed by unrecognizable text, the number is converted and returned, and the following text is silently ignored. Otherwise, the return value is 0, and the text is silently ignored. Thus, number("123abc") returns 123, and number("abc") returns 0.
This function is an inverse of hexfp(), hexint(), and string():
number(hexfp(x)) == x [for all numeric x] number(hexint(x)) == x [for all numeric x] number(string(x)) == x [for all numeric x]
See also help_hexint(), help_hexfp(), and help_string().
See also help_cd(), help_dirs(), help_pushd(), help_pwd(), and help_xd().
Matching is similar to UNIX shell pattern matching: asterisk (*) matches zero or more characters, and query (?) matches any single character. A square-bracketed list of characters, and/or hyphen-separated character ranges, matches any character in that list. A right bracket can be in the list only if it appears first. Thus, [A-Za-z0-9] matches an English letter or digit, and [][] matches a square bracket.
To match all environment variables, use printenv("*").
See also help_cd(), help_dirs(), help_popd(), help_pwd(), and help_xd().
This affects subsequent calls to getenv(), but does not affect the environment of the parent process.
You can use this function to set locale environment variables that control the output of dates and times, in order to get internationalized output from strftime().
See also help_cd(), help_dirs(), help_popd(), help_pushd(), and help_xd().
See help_randint() for uniformly-distributed integers in an interval, and help_randl() for logarithmically-distributed pseudo-random numbers.
The pseudo-random generator algorithm is platform-independent, allowing reproduction of the same number sequence on any computer architecture.
The pseudo-random generator algorithm is platform-independent, allowing reproduction of the same number sequence on any computer architecture.
This function can be used to generate logarithmic distributions on any interval: a*randl(ln(b/a)) is logarithmically distributed on (a...b).
The pseudo-random generator algorithm is platform-independent, allowing reproduction of the same number sequence on any computer architecture.
Only symbols whose names match pattern are saved.
Matching is similar to UNIX shell pattern matching: asterisk (*) matches zero or more characters, and query (?) matches any single character. A square-bracketed list of characters, and/or hyphen-separated character ranges, matches any character in that list. A right bracket can be in the list only if it appears first. Thus, [A-Za-z0-9] matches an English letter or digit, and [][] matches a square bracket.
To match all symbols, use save(filename,"*").
Symbols are output in strict lexicographic order.
Reserved symbol names (those beginning with two or more underscores) are not saved. Predefined immutable names are also excluded.
The saved file is a normal text file that can be later read by hoc on any platform.
[NB: A temporary implementation restriction also excludes user-defined immutable names, and all functions and procedures.]
This command can be disabled for security reasons by the command-line -no-save option.
The return value is an empty string on success, and otherwise, an error message.
PREC = 3 x = 1 t = second() for (k = 1; k < 1000000; ++k) x *= 1 second() - t 4.73
/usr/local/share/lib/hoc/hoc-7.0.6.beta
in this installation.
Since set_locale() is a long name, up to three shorthand procedures are provided for each language: the two-letter country code, the native name for the language, and the English name for the language. Thus, da(), dansk(), and danish() all switch to the Danish locale, and en(), engelsk(), and english() switch to the default English locale.
As a special case, when x is zero, x is ignored, and a new seed is constructed from a random number multiplied by either the calendar time (if available), or the process number (if available), or the next pseudo-random number.
If setrand(x) is never called, then rand(), randint(), and randl(x) will each return the same sequence of pseudo-random numbers: see help_rand(), help_randint(), and help_randl().
The pseudo-random generator algorithm is platform-independent, allowing reproduction of the same number sequence on any computer architecture.
See help_exponent() for how to extract the exponent, n.
By contrast, the predefined constants SNAN and SNaN have fixed bit patterns.
See also ftoh(), htof(), NaN, QNaN, and SNaN.
Special case: sqrt(-0) \(-> -0.
- %A
- the locale's full weekday name.
- %a
- the locale's abbreviated weekday name.
- %B
- the locale's full month name.
- %b
- the locale's abbreviated month name.
- %c
- the locale's appropriate date and time representation.
- %d
- the day of the month as a decimal number (01\(mi31).
- %H
- the hour (24-hour clock) as a decimal number (00\(mi23).
- %I
- the hour (12-hour clock) as a decimal number (01\(mi12).
- %j
- the day of the year as a decimal number (001\(mi366).
- %M
- the minute as a decimal number (00\(mi59).
- %m
- the month as a decimal number (01\(mi12).
- %p
- the locale's equivalent of either ``AM'' or ``PM''.
- %S
- the second as a decimal number (00\(mi60).
- %U
- the week number of the year (Sunday as the first day of the week) as a decimal number (00\(mi53).
- %W
- the week number of the year (Monday as the first day of the week) as a decimal number (00\(mi53).
- %w
- the weekday (Sunday as the first day of the week) as a decimal number (0\(mi6).
- %X
- the locale's appropriate time representation.
- %x
- the locale's appropriate date representation.
- %Y
- the year with century as a decimal number.
- %y
- the year without century as a decimal number (00\(mi99).
- %Z
- the time zone name.
- %%
- is replaced by `%'.
See also help_hexfp(), help_hexint(), and help_number().
Which characters are considered uppercase depends on the locale. On UNIX, this is determined by the LC_CTYPE environment variable.
Which characters are considered lowercase depends on the locale. On UNIX, this is determined by the LC_CTYPE environment variable.
Matching is similar to UNIX shell pattern matching: asterisk (*) matches zero or more characters, and query (?) matches any single character. A square-bracketed list of characters, and/or hyphen-separated character ranges, matches any character in that list. A right bracket can be in the list only if it appears first. Thus, [A-Za-z0-9] matches an English letter or digit, and [][] matches a square bracket.
To print all symbols, use who("*").
See also help_cd(), help_dirs(), help_popd(), help_pushd(), and help_pwd().
- annuity
- Simple financial computations with functions annuity() and compound(), and procedure mortgage().
- fortune
- Numeric fortune cookies, with procedures fortune() and findfortune().
- primes
- Prime number support, with functions isprime(), next_prime(), nth_prime(), prev_prime(), this_or_next_prime(), and this_or_prev_prime(), and procedures prime_factors() and primes_between().
- pushd
- Procedures dirs(), popd(), pushd(), and xd(). [This library is useful enough that it is preloaded by default.]
- require
- Procedures provide() and require() for loading only libraries that have not already been loaded.
- show-strftime
- Procedure show_strftime_conversions() to test all of the format items provided by the strftime() function.
- sunmath
- Additional functions modeled on ones available in the Sun Solaris mathematical library: exp10(), exp2(), iszero(), max_normal(), max_subnormal(), min_normal(), min_subnormal(), quiet_nan(), signaling_nan(), and signbit().
The current sizes of these internal storage areas are recorded as immutable numeric named constants:
- __MAX_FRAME__
- Function/procedure call stack size.
- __MAX_LINE__
- Input line buffer size.
- __MAX_NAME__
- Longest identifier name.
- __MAX_PROG__
- hoc virtual machine code size.
- __MAX_PUSHBACK__
- Input pushback buffer size.
- __MAX_STACK__
- Argument stack size.
- __MAX_STRING__
- Longest character string constant.
- __MAX_TOKEN__
- Longest numeric token.
This list may change during hoc development, but will ultimately be stable.
The function help_limits() can be conveniently used to display their current values.
func gcd(i,j) {
## gcd(i,j) returns the greatest common denominator of i and j
temp = abs(i) % abs(j)
if(temp == 0) return abs(j)
return gcd(j, temp)
}
for(i=1; i<12; i++) print gcd(i,12)
print "\n"
1 2 3 4 1 6 1 4 3 2 1
### Print a table of the representable negative powers of 2
k = 0
x = 1
while (x > 0) \
{
print "2\^(", k, ") = ", x, "\n"
k--
x /= 2
}
2^(0 ) = 1
2^(-1 ) = 0.5
2^(-2 ) = 0.25
2^(-3 ) = 0.125
...
2^(-1072 ) = 1.9762625833649862e-323
2^(-1073 ) = 9.8813129168249309e-324
2^(-1074 ) = 4.9406564584124654e-324
(LN is replaced by the locale name (see the INTERNATIONALIZATION section above), if one is defined, and otherwise, that file is omitted), and a private initialization file,
- /usr/local/share/lib/hoc/hoc-7.0.6.beta/hoc.rc,
- /usr/local/share/lib/hoc/hoc-7.0.6.beta/locale/LN/hoc.rc,
- /usr/local/share/lib/hoc/hoc-7.0.6.beta/help.hoc,
- /usr/local/share/lib/hoc/hoc-7.0.6.beta/locale/LN/help.hoc,
- /usr/local/share/lib/hoc/hoc-7.0.6.beta/translations.hoc,
- /usr/local/share/lib/hoc/hoc-7.0.6.beta/locale/LN/translations.hoc,
in that order. Any that exist are automatically processed before the remaining command-line options are handled.
- $HOME/.hocrc,
This feature allows for local customization of hoc, usually for additional constants and functions, as well as for locale-specific translations of output strings.
In initialization files, the load(), logfile(), and save() commands are always available, even if command-line options disable them from use later in the job.
If GNU readline library support is available in hoc, then its initialization file, $HOME/.inputrc, (overriddable by setting an alternate filename in the value of the INPUTRC environment variable), can be used for customization of key bindings for command completion, editing, and recall. To restrict any such bindings to hoc, put them in a conditional like this:
$if hoc
...
$endif
Brian W. Kernighan and Rob Pike, The UNIX Programming Environment Prentice-Hall, Upper Saddle River, NJ (1984) ISBN 0-13-937699-2 (hardcover), 0-13-937681-X (paperback), LCCN: QA76.76.O63 K48 1984.
Sadly, most programming language textbooks have little or no coverage of floating-point arithmetic, and programming language standards, besides being hard to read, have generally provided inadequate support for IEEE 754 arithmetic.
An early draft of the IEEE 754 Standard was published in an October 1979 special issue of ACM SIGNUM Newsletter. The January 1980 and March 1981 issues of the IEEE journal Computer contain several papers about the then-developing IEEE 754 proposal, including a draft of the Standard.
The official IEEE 754 Standard is available as:
Work on a revision of that Standard began about 2000, and is expected to take several years.ANSI/IEEE 754-1985, Standard for Binary Floating-Point Arithmetic IEEE, New York, NY (1985) 20 pp. ISBN 1-55937-653-8
An interestingly account of the early development of the IEEE 754 arithmetic system can be found in the Web document
Charles Severance An Interview with the Old Man of Floating-Point: Reminiscences elicited from William Kahan URL http://www.cs.berkeley.edu/~wkahan/ieee754status/754story.html
The IEEE sponsors symposia on computer arithmetic that are held approximately every other year; the 15th was held in 2001. Most of the papers deal with low-level hardware issues of computer arithmetic.
The journal Communications of the ACM began publishing computer algorithms in 1960, and in 1974, that function was moved to a new journal, ACM Transactions on Mathematical Software. That journal, TOMS for short, has become the principal publication source for computer software that implements numerical algorithms. Other important journals in this area include Computing, Mathematics of Computation, and Numerische Mathematik (whose articles are mostly in English, despite the German title); their emphasis is often heavily theoretical.
A recent short book that discusses IEEE 754 arithmetic exclusively is:
Michael Overton
Numerical Computing with IEEE Floating Point Arithmetic, Including One Theorem, One Rule of Thumb, and One Hundred and One Exercisesxiv + 104 pp. SIAM, Philadelphia, PA (2001) ISBN 0-89871-482-6 LCCN QA76.9.M35 O94 2001
Two recent books about hardware implementation of computer arithmetic are:
Amos R. Omondi Computer Arithmetic Systems --- Algorithms, Architecture, Implementation Prentice-Hall, Upper Saddle River, NJ (1994) xvi + 520 pp. ISBN 0-13-334301-4 LCCN QA76.9.C62 O46 1994 Behrooz Parhami Computer Arithmetic: Algorithms and Hardware Designs Oxford University Press, Oxford, UK (2000) xx + 490 pp. ISBN 0-19-512583-5 LCCN QA76.9.C62P37 1999
The older book
remains a good reference for the accurate computation of the elementary functions, and is one of the few to address the related issue of decimal floating-point systems (such as used in some hand calculators). Its elementary function test package, ELEFUNT, exposed serious flaws in a great many vendor implementations, and thanks to ELEFUNT, today, the accuracy and reliability of the revised implementations is very much better. Although the book was written before IEEE 754 arithmetic became available, in many cases, only simple tests for NaN and Infinity arguments need to be inserted into the start of each algorithm to generalize the code for current systems.William J. Cody, Jr. and William Waite Software Manual for the Elementary Functions Prentice-Hall, Upper Saddle River, NJ (1980) x + 269 pp. ISBN 0-13-822064-6 LCCN QA331 .C635 1980
A excellent recent book that addresses computation of the elementary functions on a particular extended implementation of IEEE 754 arithmetic, that in the HP/Intel IA-64 architecture, is
Markstein's book also contains algorithms for the correctly-rounded computation of floating-point division and square-root, and of integer division, starting from low-precision reciprocal approximations.Peter Markstein IA-64 and Elementary Functions: Speed and Precision xix + 298 pp. Prentice-Hall, Upper Saddle River, NJ (2000) ISBN 0-13-018348-2 LCCN QA76.9.A73 M365 2000
Error recovery is imperfect within function and procedure definitions.
The treatment of newlines is not exactly user-friendly.
Function/procedure arguments, whether named or numbered ($1, $2, ...) are not really variables and thus won't work in constructs like, for instance, $1++.
Functions and procedures typically have to be declared before use, which makes mutual recursion at first sight impossible. The workaround is to first define a dummy version of one of them. For example, here is an unusual implementation of a pair of functions, each of which returns the factorial of its argument:
func foo() return 0
func bar(n) {if (n > 0) return n * foo(n-1) else return 1}
func foo(n) {if (n > 0) return n * bar(n-1) else return 1}
For platforms where suitable compilers are often not installed, there may be binary distributions available at those locations.ftp://ftp.math.utah.edu/pub/hoc http://www.math.utah.edu/pub/hoc/
Copyright (C) AT&T 1995 All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that the copyright notice and this permission notice and warranty disclaimer appear in supporting documentation, and that the name of AT&T or any of its entities not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. AT&T DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL AT&T OR ANY OF ITS ENTITIES BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
He also thanks the many people at the Free Software Foundation, for enriching UNIX with GNUware, and most notably, Richard Stallman for emacs(1) and gcc(1), for founding the FSF and the GNU Project, and for vigorous campaigning to keep software freely distributable.
Finally, he thanks friends and colleagues on the hoc help facility translation team for assistance in internationalization: Hugo Bertete-Aguirre (Portuguese), Andrej Cherkaev (Russian), Tanya Damjanovic (Serbian), Michel Debar (French), Miguel Dumett (Spanish), Henryk Hecht (Polish), Michael Hohn (German), Ismail K�����k (Turkish), Young Seon Lee (Korean), Dragan Milicic (Croatian), and Jingyi Zhu (Chinese). [The English and Danish, and part of the French, help facilities were written by the maintainer.]