File: 5-22-89-notes.text

package info (click to toggle)
gcl 2.6.7%2Bdfsga-1
  • links: PTS
  • area: main
  • in suites: wheezy
  • size: 84,796 kB
  • sloc: ansic: 452,686; lisp: 156,133; asm: 111,405; sh: 29,299; cpp: 18,599; perl: 5,602; makefile: 5,201; tcl: 3,181; sed: 469; yacc: 378; lex: 174; fortran: 48; awk: 30; csh: 23
file content (152 lines) | stat: -rw-r--r-- 5,394 bytes parent folder | download | duplicates (17)
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
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
Copyright (c) Xerox Corporation 1989. All rights reserved.

These notes correspond to the "5/22/89 Victoria PCL" version of PCL.

Please read this entire file carefully.  Failure to do so guarantees
that you will have problems porting your code from the previous release
of PCL.

You may also be interested in looking at previous versions of the
notes.text file.  These are called xxx-notes.text where xxx is the
version of the PCL system the file corresponds to.  At least the last
two versions of this file contain useful information for any PCL user.

This version of PCL has been tested at PARC in the following Common
Lisps:

  Symbolics 7.2, 7.4
  Coral 1.2
  Lucid 3.0
  IBCL (October 15, 1987)
  Allegro 3.0.1
  Golden Common Lisp 3.1
  EnvOS Medley

These should work, but haven't been tested yet:

  TI

This release is similar to Cinco de Mayo and Passover PCL.  The major
difference is that this release actually works.

***

*other-exports* flushed.  More exports now on *exports*

The symbol STANDARD is now exported from the PCL package. standard-class
standard-method standard-generic-function standard-object built-in-class
structure-class

scoping problem with *next-methods*


method and generic function initialization protocol

methods are immutable

type-specifiers --> specializers

load-truename etc.

defgeneric ensure-generic-function define-method-combination

metabraid changes

file namings

***

There are a number of minor and one major difference between this
release and No Cute Name PCL.


- In the last release there was an implementation of the specified CLOS
initialization protocol.  This implementation had the correct behavior,
but some of the generic functions had temporary names (*make-instance,
*initialize-instance and *default-initargs).  This was done to give
people time to convert their code to the behavior of the new
initialization protocol.

In this release, all generic functions in the specified initialization
protocol have their proper names.  The implementation of the old,
obsolete initialization protocol has disappeared entirely.

The following renamings have happened:

  12/7/88 release                this release

  *make-instance                 make-instance
  *initialize-instance           initialize-instance
  *default-initargs              default-initargs

The functions shared-initialize and reinitialize-instance already had
the proper names.

The new initialization protocol is documented fully in the 88-002R
specification.

As part of this change, PCL now uses the new initialization protocol to
create metaobjects internally.  That is it calls make-instance to create
these metaobjects.  The actual initargs passed are not yet as specified,
that will be in a later release.

This is the largest change in this release.  If you have not already
started using the new initialization protocol (with the temporary *xxx
names) you are going to have to do so now.  In most cases, old methods
on the generic functions INITIALIZE, INITIALIZE-FROM-DEFAULTS and
INITIALIZE-FROM-INIT-PLIST must be substantially rewritten to convert
them to methods on INITIALIZE and SHARED-INITIALIZE.

- slots with :ALLOCATION, :CLASS now inherit properly.  As part of this
change, some slot description objects now return a class object as the
result of SLOTD-ALLOCATION.

- There is now a minimal implementation of the DEFGENERIC macro.  This
implementation supports no options, but it does allow you to define a
generic function in one place and put some comments there with it.

- The following functions and macros have disappeared.  This table also
  show briefly what you use instead.

    DEFMETHOD-SETF               (use DEFMETHOD)
    RUN-SUPER                    (use CALL-NEXT-METHOD)
    OBSOLETE-WITH-SLOTS          (use WITH-SLOTS or WITH-ACCESSORS)
    SYMBOL-CLASS                 (use FIND-CLASS)
    CBOUNDP                      (use FIND-CLASS)
    CLASS-NAMED                  (use FIND-CLASS)
    GET-SETF-GENERIC-FUNCTION    (use GDEFINITION)

- In certain ports, method lookup will be faster because of a new scheme
to deal with interrupts and the cache code.  In other ports it will be
slightly slower.  In all ports, the cache code now interacts properly
with interrupts.

- DEFMETHOD should interact properly with TRACE, ADVISE etc. in most
ports.  two new port-specific functions (in defs.lisp) implement this.
These are unencapsulated-fdefinition and fdefine-carefully.  If this
doesn't work properly in your port, fix the definition of these
functions and send it back so it can be in the next release.

- This release runs in Golden Common Lisp version 3.0.

- Previously, the use of slot-value (or with-slots) in the body of a
method which had an illegal specializer gave strange errors.  Now it
gives a more reasonable error message.

- An annoying problem which caused KCL and friends to complain about
*exports* being unbound has been fixed.

- The walker has been modified to understand the ccl:%stack-block
special form in Coral Common Lisp.

- The use of defadvice in pre 3.0 releases has been fixed in Lucid Low.

- multiple-value-setq inside of with-slots now returns the correct
value.

- A minor bug having to do with macroexpansion environments and the KCL
walker has been fixed.

- A bug in the parsing of defmethod which caused only symbols (rather
than non-nil atoms) to be used as qualifiers.