Variable | Package: compiler | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version

## verify-funcalls-switch

As with most compiler switch variables, the value of this variable can be `t`, `nil`, or a function object that accepts five arguments and returns `t` or `nil`. The arguments passed to the function will be the values of the safety, space, speed, debug, and compilation-speed optimization qualities, in that order. `nil` is equivalent to a function that always returns `nil` and `t` to a function that always returns `t`. When the value is a function and we say `t` (or true) or `nil` (or false) in the text below, we mean that the function returns, respectively, `t` or `nil`.

If false, funcall's of objects which are known to be funcall'able at compile time will be compiled in such a way that the jump is directly to the function start addresses. This speeds up funcall'ing but at the cost of easier debugging (as stepping and profiler call counting will not work). That is why this variable is true for debug values other than 0. Initially true (i.e. slower funcall's) if speed is less than 3 or if safety is greater than 1 or if debug is greater than 0.

In the 7.0 release, this switch is not effective on all ports. (It is simply ignored on ports where it is not implemented.)

See compiling.htm for information on the compiler.

Copyright (c) 1998-2022, Franz Inc. Lafayette, CA., USA. All rights reserved.
This page was not revised from the 10.0 page.
Created 2019.8.20.

|  | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version