From 848806b80e5e112ce3a06ace11e8bf6518048c9d Mon Sep 17 00:00:00 2001 From: "Guillermo J. Rozas" Date: Mon, 1 Oct 1990 22:17:05 +0000 Subject: [PATCH] Add a note about integrations. --- v7/src/compiler/documentation/safety.txt | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/v7/src/compiler/documentation/safety.txt b/v7/src/compiler/documentation/safety.txt index 07608c03f..a266b9c17 100644 --- a/v7/src/compiler/documentation/safety.txt +++ b/v7/src/compiler/documentation/safety.txt @@ -1,6 +1,6 @@ -*- Text -*- -$Header: /Users/cph/tmp/foo/mit-scheme/mit-scheme/v7/src/compiler/documentation/safety.txt,v 1.1 1990/09/29 23:00:31 jinx Exp $ +$Header: /Users/cph/tmp/foo/mit-scheme/mit-scheme/v7/src/compiler/documentation/safety.txt,v 1.2 1990/10/01 22:17:05 jinx Exp $ COMPILER SAFETY INFORMATION Liar versions 4.77 and later @@ -121,6 +121,15 @@ Some important considerations: generated code corresponding to a primitive call, whether open coded or not, will operate correctly on correct inputs. +- If the compiler does not know that the operator of a combination is +a primitive procedure, it will not open code it. In particular, if +the compiler does not know that a variable is bound to a particular +primitive procedure, no combinations with that variable as the +operator will be open coded. Usually the compiler is informed of such +constant bindings by making use of declarations like +USUAL-INTEGRATIONS. See the documentation for sf for additional +information on declarations. + - The compiler will not make an unsafe program safe, ie. safe translation does not compensate for unsafe programs. -- 2.25.1