File: README.md

package info (click to toggle)
acl2 8.6%2Bdfsg-2
  • links: PTS
  • area: main
  • in suites: trixie
  • size: 1,111,420 kB
  • sloc: lisp: 17,818,294; java: 125,359; python: 28,122; javascript: 23,458; cpp: 18,851; ansic: 11,569; perl: 7,678; xml: 5,591; sh: 3,976; makefile: 3,833; ruby: 2,633; yacc: 1,126; ml: 763; awk: 295; csh: 233; lex: 197; php: 178; tcl: 49; asm: 23; haskell: 17
file content (82 lines) | stat: -rw-r--r-- 2,785 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
# global-vars

Define efficient global variables in Common Lisp.

## Synopsis

    ;; Similar to defparameter with regard to redefinitions
    (define-global-parameter -x- 3)

    ;; Similar to defvar with regard to redefinitions
    (define-global-var -y- 4)

    ;; ...

    (setf -x- 5)
    (setf -y- 6)

## Description

In Common Lisp, a special variable that is never dynamically bound
typically serves as a stand-in for a global variable. The
`global-vars` library provides true global variables that are
implemented by some compilers. An attempt to rebind a global variable
properly results in a compiler error. That is, a global variable
cannot be dynamically bound.

Global variables therefore allow us to communicate an intended usage
that differs from special variables. Global variables are also more
efficient than special variables, especially in the presence of
threads.

## API

* [macro] **`define-global-var`** `name` `value` *`&optional`* `documentation`

  Define a global variable with a compile-time value.

  Subsequent redefinitions will not change the value (like `defvar`).

  The `value` argument is evaluated at compile-time. On SBCL, this
  permits optimizations based upon the invariant that `name` is always
  bound.

* [macro] **`define-global-var*`** `name` `value` *`&optional`* `documentation`

  Same as `define-global-var` except `value` is evaluated at load time,
  not compile time.

* [macro] **`define-global-parameter`** `name` `value` *`&optional`* `documentation`

  Same as `define-global-var` except subsequent redefinitions will
  update the value (like `defparameter`).

* [macro] **`define-global-parameter*`** `name` `value` *`&optional`* `documentation`

  Same as `define-global-parameter` except `value` is evaluated at
  load time, not compile time.

## Detail

`global-vars` wraps the following implementation-specific features:

* [SBCL](http://www.sbcl.org/manual/#Global-and-Always_002dBound-variables): `sb-ext:defglobal` and `sb-ext:define-load-time-global`.

* [CCL](http://ccl.clozure.com/manual/chapter4.8.html): `ccl:defstatic` and `ccl:defstaticvar`.

* [LispWorks](http://www.lispworks.com/documentation/lw61/LW/html/lw-122.htm): `hcl:special-global`, in particular `defglobal-parameter` and `defglobal-variable`.

For these implementations, rebinding a global variable is a
compilation error.

On other implementations, a global variable is implemented as a symbol
macro which expands to a `symbol-value` form. Rebinding a global
variable will (unfortunately) not signal an error.

It is recommended to use a naming convention for global variables,
such as `-foo-`. This makes it clear that `(let ((-foo- 9)) ...)` is a
mistake even if the compiler doesn't catch it.

## Author

James M. Lawrence <llmjjmll@gmail.com>