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