4 ** *.pure.lisp tests run with assertoid.lisp loaded; assertoid
5 is moved to its own package, for use in *.impure.lisp.
6 ** non-x86 ports now pass irrat.pure.lisp
7 ** sparc and ppc now pass bit-vector.impure-cload.lisp
8 * faster bootstrapping (both make.sh and slam.sh)
9 ** added mechanisms for automatically finding dead code, and
10 used them to remove dead code
11 ** moved stuff from warm init into cold init where possible
12 (so that slam.sh will run faster and also just because
13 ideally everything would be in cold init)
14 ** profiled and tweaked
15 * fixed (TRACE :REPORT PROFILE ...) interface to profiling
16 * more EVAL/EVAL-WHEN/%COMPILE/DEFUN/DEFSTRUCT cleanup:
17 ** made %COMPILE understand magicality of DEFUN FOO
18 w.r.t. e.g. preexisting inlineness of FOO
19 ** used %COMPILE where COMPILE-TOP-LEVEL used to be used
20 ** removed now-redundant COMPILE-TOP-LEVEL and
21 FUNCTIONAL-KIND=:TOP-LEVEL stuff from the compiler
22 ** (ideally, but perhaps too hard, given what I've discovered
23 about the godawful internals of function debug names):
24 made FUNCTION-NAME logic work on closures, so that
25 various public functions like CL:PACKAGEP which
26 are now implemented as closures (because
27 they're structure slot accessors) won't be so
29 * outstanding embarrassments
30 ** :IGNORE-ERRORS-P cruft in stems-and-flags.lisp-expr. (It's
31 reasonable to support this as a crutch when initially
32 bootstrapping from balky xc hosts with their own
33 idiosyncratic ideas of what merits FAILURE-P, but it's
34 embarrassing to have to use it when bootstrapping
36 * fixups now feasible because of pre7 changes
37 ** ANSIfied DECLAIM INLINE stuff (deprecating MAYBE-INLINE,
38 including e.g. on the man page)
39 * miscellaneous simple refactoring
41 ** renamed %PRIMITIVE to %VOP
42 * These days ANSI C has inline functions, so..
43 ** redid many cpp macros as inline functions:
44 HeaderValue, Pointerp, CEILING, ALIGNED_SIZE,
45 GET_FREE_POINTER, SET_FREE_POINTER,
46 GET_GC_TRIGGER, SET_GC_TRIGGER, GetBSP, SetBSP,
47 os_trunc_foo(), os_round_up_foo()
48 ** removed various avoid-evaluating-C-macro-arg-twice
50 * Either get rid of or at least rework the fdefinition/encapsulation
51 system so that (SYMBOL-FUNCTION 'FOO) is identically equal to
53 =======================================================================
56 * refactored in preparation for moving CLOS into cold init and merging
57 SB-PCL:FOO with CL:FOO (for FOO=CLASS, FOO=CLASS-OF, etc.)
58 ** systematized support for MOP (new regression tests, maybe
59 new SB-MOP package..) to try to make sure things don't
60 get mislaid in the upcoming CLOS restructuring
61 ** extracted type system from SB-KERNEL into new SB-TYPE
63 ** reimplemented GENERIC-FUNCTION as a primitive object (or
64 maybe made SB-MOP:FUNCALLABLE-STANDARD-OBJECT the
65 primitive object, and then let GENERIC-FUNCTIONs
66 inherit from that) instead of structures with
67 :ALTERNATE-METACLASS and funcallableness. Now
68 FUNCALLABLE-INSTANCE can go away. (And now the new
69 funcallable primitive objects need to go into
70 collections like *FUN-HEADER-WIDETAGS* where
71 FUNCALLABLE-INSTANCE objects used to be.)
72 ** reimplemented CONDITIONs as primitive objects instead of
73 structures with :ALTERNATE-METACLASS. Now (between
74 this and the change to GENERIC-FUNCTIONs)
75 DEFSTRUCT :ALTERNATE-METACLASS can go away.
76 ** (maybe) Now INSTANCE_POINTER_LOWTAG can become just
77 STRUCTURE_POINTER_LOWTAG, and the concept of
78 SB-KERNEL:INSTANCE (including INSTANCEP,
79 (SPECIFIER-TYPE 'INSTANCE), etc.) can go away.
80 * moved CLOS into cold init, in order to allow CLOS to be used in the
81 implementation of the core system (e.g. the type system and the
82 compiler) and in order to support merger of CL:CLASS with
84 * (maybe) eliminated warm init altogether in favor of cold init
85 * (maybe, especially if warm init can be eliminated) rationalized
86 the build process, fixing miscellaneous pre-0.5.0 stuff that's
87 transparently not the right thing
88 ** removed separate build directories, now just building in
89 place with .sbclcoldfasl extensions
90 * (maybe) more refactoring in preparation for merging SB-PCL:FOO
91 into CL:FOO: reimplemented type system OO dispatch
92 (!DEFINE-TYPE-METHOD, etc.) in terms of CLOS OO dispatch
93 * merged SB-PCL:FOO into CL:FOO (and similarly CLASS-OF, etc.)
94 * added some automatic tests for basic binary compatibility, in hopes
95 that it might be practical to maintain binary compatibility
96 between minor maintenance releases on the stable branch (but no
97 promises, sorry, since I've never tried to do this before, and
98 have no idea how much of a pain this'll be)
99 ========================================================================
100 for 1.0 (fixes of lower priority which I'd nonetheless be embarrassed
101 to leave unfixed in 1.0):
102 * all too many BUGS entries and FIXMEs
103 =======================================================================
104 other priorities, no particular time:
106 * bug fixes, especially really annoying bugs (ANSI or not) and any
107 ANSI bugs (i.e. not just bugs in extras like the debugger or
108 "declarations are assertions", but violations of the standard)
109 * better communication with the outside world (scratching WHN's
110 personal itch): I don't want socket-level stuff so much as I
111 want RPC-level or higher (CORBA?) interfaces and (possibly
112 through RPC or CORBA) GUI support
113 =======================================================================
114 important but out of scope (for WHN, anyway: Patches from other people
115 are still welcome!) until after 1.0:
117 * sadly deteriorated support for ANSI-style block compilation
118 (static linking of DEFUNs within a single file or
119 WITH-COMPILATION-UNIT)
120 * various GC issues (exuberant cut-and-paste coding,
121 possibly dangerously over-conservative handling
122 of neighbors of function objects, general GC efficiency)
123 * package issues other than SB!TYPE, SB!MOP, and dead exported
125 * Any systematic effort to fix compiler consistency checks is
126 out of scope. (However, it still might be possible to
127 determine that some or all of them are hopelessly stale
129 =======================================================================
130 other known issues with no particular target date:
132 bugs listed on the man page
134 hundreds of FIXME notes in the sources from WHN
136 various other unfinished business from CMU CL and before, marked with
137 "XX" or "XXX" or "###" or "***" or "???" or "pfw" or "@@@@" or "zzzzz"
138 or probably also other codes that I haven't noticed or have forgotten.
140 (Things marked as KLUDGE are in general things which are ugly or
141 confusing, but that, for whatever reason, may stay that way
143 =======================================================================
144 "There's nothing an agnostic can't do as long as he doesn't know
145 whether he believes in anything or not."
148 "God grant me serenity to accept the code I cannot change, courage to
149 change the code I can, and wisdom to know the difference."
152 "Accumulation of half-understood design decisions eventually chokes a
153 program as a water weed chokes a canal. By refactoring you can ensure
154 that your full understanding of how the program should be designed is
155 always reflected in the program. As a water weed quickly spreads its
156 tendrils, partially understood design decisions quickly spread their
157 effects throughout your program. No one or two or even ten individual
158 actions will be enough to eradicate the problem."
159 -- Martin Fowler, in _Refactoring: Improving the Design of Existing
162 "I wish I didn't know now what I didn't know then."