If allocation of memory necessary for rearrange heap failed, pi will terminate abnormally. If it is impassoble to estimate amount of heap usage and abnormal termination is not permitted, some consideration is required, such as doing a checkpoint dump occasionally and restart program by some external machanism (shell script, in example.)

The following problem arises in cygnus win32(gcc) environment 17.1beta.

• Char-ready? does not work properly.
• Unable to catch signals.
• Procedures in which floating point exception must be handled such as inexact->exact do not work properly.

The following problem arises in win32 environment(other than cygnus gcc.)

• Some odd behavior will be observed when signal is caught while waiting input.
• Some behaviors in floating point operations are not that the author intended, in example, nonsense finite value results from evaluation of (atan -i).

indexes