Commits on Jan 19, 2002
  1. integration hassles, cont'd:

    	refined my sh script technique (removing syntax errors)
    William Harold Newman committed Jan 19, 2002
  2. integration hassles, cont'd:

    	gave up on trying to mess with different versions of jade on
    		different architectures, at which point it became clear
    		that I wanted the formatted docs to be distributed in
    		a different package than source or binary, so...
    	...wrote to slurp up the HTML-formatted
    	...tweaked so it no longer slurps up the
    		HTML-formatted documentation
    William Harold Newman committed Jan 19, 2002
  3. uh, *working* on 0.7.0, anyway:

    	fixed SGML typo that OpenBSD openjade didn't care about (?)
    		but Linux jade caught
    William Harold Newman committed Jan 19, 2002
  4. 0.7.0:

    	(Woo hoo!)
    	lotso doc tweaking
    William Harold Newman committed Jan 19, 2002
Commits on Jan 18, 2002
  1. 0.pre7.142:

    	(I hope this looks a lot like 0.7.0. I'll putter on and around
    		it for a while, xc'ing under CMU CL, building some
    		applications, etc. Then if there isn't too much
    		surprise, maybe I can finally ship it!)
    	late-breaking incompatible cleanup: The default USE list
    		implementation-defined. Let's just make it NIL, the
    		way God intended, instead of trying to guess. (Anyone
    		who actually wants something random can just
    		:USE (PACKAGE-USE-LIST :CL-USER) anyway.:-) So...
    	...Implementation-defined things are supposed to be
    		documented. Put this in the doc string of MAKE-PACKAGE.
    	...Putting it in NEWS would be good too.
    William Harold Newman committed Jan 18, 2002
Commits on Jan 17, 2002
  1. 0.pre7.141:

    	made DESCRIBE output of PACKAGE data more concise
    William Harold Newman committed Jan 17, 2002
Commits on Jan 16, 2002
  1. 0.pre7.140:

    	merged SB-C-CALL into SB-ALIEN (since the rationale for
    		C-CALL being an extension of "basic" SB-ALIEN isn't
    		obviously compelling)
    	...deleted various notes about the distinction between
    		packages at egrep matches to '\<c-call'
    	...mentioned the change in the FFI quasichapter of the
    		user manual
    	...s/c-call/alien/ at matches to 'sb.c-call'
    	...remembered to add SB-C-CALL nickname for backwards
    	There seems no longer to be any reason that VOID or
    		WEAK-POINTER-P needs to be re-exported from SB-KERNEL.
    	It doesn't make all that much sense to reexport
    	Remove the old set-the-cold-package-nickname support from
    		set-up-cold-packages.lisp and friends, since it's
    		unused and not quite right anyway and much too
    		annoying to fix (messing with renaming SB!FOO
    		nicknames to SB-FOO nicknames, ick). The SB-FOO
    		nickname needed is this backwards compatibility
    		hack, and it can be hacked in at init time.
    William Harold Newman committed Jan 16, 2002
  2. 0.pre7.139:

    	more s/argument/arg/...
    	...*not* s/one-argument/one-arg/, since CL defines
    		:IDENTITY-WITH-ONE-ARGUMENT as a kw arg for
    William Harold Newman committed Jan 16, 2002
  3. 0.pre7.138:

    	merged CSR "{find,position}-if-not" patch from sbcl-devel
    	tweaked %NATURALIZE-C-STRING to reduce the ridiculous consing
    		(reported on cmucl-imp ca. 2002-01-15 by Lynn Quam) in
    		the reinvent-the-strlen() code
    	added assertion in GENESIS to try to catch "SB!"-vs.-"SB-"
    		prefix mistakes in code it works with
    William Harold Newman committed Jan 16, 2002
  4. 0.pre7.137:

    	more ARGUMENT-to-ARG abbreviation, mostly from egrepping
    		'def[^ ]* \(*[^ ]*argument'...
    	removed BUGS 130 as per CSR sbcl-devel 2002-01-16
    	cut DB's notes from CLiki SBCL internals
    		page, pasted them into comments, and rewrote
    		them some
    William Harold Newman committed Jan 16, 2002
  5. 0.pre7.136:

    	abbreviating ARGUMENT as ARG...
    	also changed ARGUMENT to ARGS in the context of ARG-COUNT-ERROR
    William Harold Newman committed Jan 16, 2002
Commits on Jan 15, 2002
  1. 0.pre7.135:

    	DO-FOO should be used for iteration names, not other things...
    	...I'm not sure enough about behavior of VOP names to mess with
    		DO-MAKE-VALUE-CELL immediately, but at least I can
    		rename the MAKE-VALUE-CELL event to MAKE-VALUE-CELL-EVENT
    		to start to untangle the names here.
    	fixed dumb oversight in debug.impure.lisp
    William Harold Newman committed Jan 15, 2002
  2. 0.pre7.134:

    	MNA "more describe (and arglist) cleanup" patch from
    		sbcl-devel 2002-01-15
    	Tweak the arglist regression tests so that they don't depend on
    		the (somewhat arbitrary) names chosen for arguments in
    		some implementation file far far away, but only on
    		supported behavior and local code.
    	Rearrange the arglist regression tests a little. (Make
    		debug.impure.lisp and move 'em there.)
    William Harold Newman committed Jan 15, 2002
  3. 0.pre7.133:

    	NJF patch I from sbcl-devel 2002-01-14: "Keywords are
    		self-evaluating, right?  They don't need to be quoted?
    		Then I wonder why the writers of PCL felt it necessary
    		to do so. This patch fixes that."
    	NJF patch II from sbcl-devel 2002-01-14: "This patch does
    		away with the strange business of the PUSHP argument to
    		DEFINE-FOP (and DEFINE-COLD-FOP) being
    		(MEMBER '(T NIL :NONE)) and implements the suggestion
    		at the top of src/code/fop.lisp for fixing it."
    	chased down ramifications of s/offs-hook-function/offs-hook-fun/,
    		as per Alexei Dejneka broken disassembler bug report
    		sbcl-devel 2001-01-14
    	the poor neglected user manual...
    	...added some information about compiler-only-ness in the
    	...removed some "I'm sorry about this bug, give me time" stuff,
    		since time has passed, and the bugs are gone:-)
    	belatedly incremented fasl file version
    William Harold Newman committed Jan 15, 2002
  4. (I seem to've screwed up during the checkin of 0.pre7.131 before, so

    that it's log message got lost. So this checkin has two log messages,
    .131 for the changes in the previous checkin and .132 for the changes
    in this checkin.)
    	s/variable/var/ in...
    	...(not set-variable because there's already a VAR slot for the
    		SET structure type, gah, so try s/set-variable/setq-var/)
    	Rename NAMED-VAR function to LOOP-NAMED-VAR, for consistency
    		with other LOOP operators and with the LOOP comments
    		which refer to LOOP-NAMED-VAR.
     	learning that I don't even get people's *names* right
    		in CREDITS:-(
    	addressed APD bug report 2001-01-13...
    	...made a BUGS entry for pretty-printing nested backquotes
    	...scattered references to compiler-only implementation
    		through doc/sbcl.1
    	other corrections and tweaks in doc/sbcl.1
    William Harold Newman committed Jan 15, 2002
Commits on Jan 14, 2002
  1. *** empty log message ***

    William Harold Newman committed Jan 14, 2002
  2. 0.pre7.129:

    	s/function/fun in...
    William Harold Newman committed Jan 14, 2002
Commits on Jan 13, 2002
  1. 0.pre7.128:

    	MNA "patch for bug 105 and some other cleanups" (sbcl-devel
    	...fixed bug 105: made (DESCRIBE 'STREAM-READ-CHAR) work right
    		even when there're no methods on the GF yet
    	...tweaked format of DESCRIBE of methods, simplifying
    	...tidied up tests/ stuff, deleting temporary files after use
    	...deleted BUGS entries (105 entry, and stale 99 entry too)
    	tweaked MNA patch...
    	...explicitly saying "It has no methods." for bare GF
    William Harold Newman committed Jan 13, 2002
  2. 0.pre7.127:

    	(There were >300 matches to
    		"egrep -sn '^\(def[^(;&]*function' ..." before.)
    	not just s/function/fun/, but also clearing up mess of (1)
    		LOSSAGE/SLIME (esp. SLIME), what do they mean? and
    		(2) "ERROR" and "WARNING" used in names even though
    		the condition system isn't involved...
    	other confusion/inconstency...
    	...s/compiler-style-warning/compiler-style-warn/ when used
    		as verb (as opposed to used as condition name)
    	...and similarly for s/compiler-warning/compiler-warn/
    	(There are now some 230 hits to the egrep at the start, mostly in
    		src/pcl/*, where I'm trying to tread lightly to avoid
    		gratuitously breaking quasistandard MOPish things.)
    William Harold Newman committed Jan 13, 2002
  3. 0.pre7.126:

    	even more s/#'(lambda/(lambda/ (should be done now)
    William Harold Newman committed Jan 13, 2002
Commits on Jan 12, 2002
  1. 0.pre7.125:

    	more s/#'(lambda/(lambda/
    William Harold Newman committed Jan 12, 2002
  2. 0.pre7.124:

    	lotso s/#'(lambda/(lambda/
    William Harold Newman committed Jan 12, 2002
  3. 0.pre7.123:

    	NJF save.lisp buglet fix sbcl-devel 2002-01-11
    	MNA "patch for bug 99" sbcl-devel 2002-01-11 (includes symbol
    		and cleanups too, not just bug 99)
    William Harold Newman committed Jan 12, 2002
  4. 0.pre7.122:

    	belatedly removed BUGS entry 38 (fixed by MNA in 0.pre7.120)
    	Now that bug 138 is fixed, I can s/#'(lambda/(lambda/ to my
    		heart's content -- in theory. But what have we here,
    		another bizarre xc bug? Apparently. So...
    	...added #!+SB-SHOW ID slot to some fundamental compiler data
    	...(eventually found that MULTIPLE-VALUE-BIND macro definition
    		is sensitive to s/#'(lambda/(lambda/, which sorta
    		makes sense)
    William Harold Newman committed Jan 12, 2002
Commits on Jan 10, 2002
  1. NJF DOLIST/MACROLET patch for vmtran (sbcl-devel 2002-01-07,

    		revised 2002-01-08)
    William Harold Newman committed Jan 10, 2002
  2. 0.pre7.120:

    	MNA patch for bug 38 (sbcl-devel 2002-01-07)
    	removed BUGS entries 18 and 29 as per MNA sbcl-devel 2002-01-07
    William Harold Newman committed Jan 10, 2002
  3. 0.pre7.119:

    	CR patch for bug 139 and other DIRECTORY badness (sbcl-devel
    	TMPDIR tweak suggested by CR sbcl-devel 2001-12-31
    	enabled various test cases for DIRECTORY now that they work
    	Enable test cases.
    	Remove or at least weaken BUGS entry.
    William Harold Newman committed Jan 10, 2002
Commits on Jan 9, 2002
  1. 0.pre7.118:

    	fixed FIXME in RECOGNIZE-KNOWN-CALL, since the new type test is
    		shorter than the old FIXME explanation
    	fixed bug 138 by making FIND-FREE-FUNCTION pickier about
    		reusing things from other components (testing
    	Remove REMOVEMEs.
    	Test building the compiler with itself.
    William Harold Newman committed Jan 9, 2002
Commits on Jan 7, 2002
  1. 0.pre7.117:

    	encapsulated (OR (COMPONENT-FOO ...) ...) idiom in IR1-PHASES
    	made TRACE :PRINT use pretty-printed line breaks to keep
    		indentation sane
    	added more checks related to bug 138, including restoring the
    		strength of the original LOCALL-ANALYZE-COMPONENT
    		assertion so that I'm back to debugging 138a again:-|
    		(It's too bad I didn't have the courage of my
    		convictions lo these many hours of debugging ago, to
    		keep my strong 138a assertion and immediately chase
    		back whatever weirdness causes it to fail, instead of
    		weakening it and painfully debugging the
    William Harold Newman committed Jan 7, 2002
Commits on Jan 6, 2002
  1. 0.pre7.115:

    	minor tweak in the new names: "SB-INT:&MORE processor for FOO"
    		is unnecessarily cryptic, and maybe
    		"varargs entry point for FOO" is better
    	bug 138, continued: It seems bad for WITH-BELATED-IR1-ENVIRONMENT
    		to be binding *CURRENT-COMPONENT* to something which has
    		already had COMPILE-COMPONENT called on it once and for
    		all. I added checks to stop this...
    			(instead of just NILing it out)
    		...added some assertions that key operations aren't
    			applied to dead components
    William Harold Newman committed Jan 6, 2002
  2. 0.pre7.114:

    	more name tweaks...
    	...If we do use an abbreviation, I'd like it to be used
    		consistently. s/xep/external-entry-point/ looks too
    		ouch) so s/external-entry-point/xep/ instead.
    	fixed the "&MORE processor" function debug name syndrome...
    	...added SOURCE-NAME and DEBUG-NAME arguments to the
    		various IR1-CONVERT-FOO functions running up to
    		...IR1-CONVERT-MORE itself
    	...made IR1-CONVERT-MORE use the names to make a debug
    		name which identifies the parent function bonus: made IR1-CONVERT-HAIRY-ARGS use
    		SOURCE-NAME and DEBUG-NAME to build a better
    		(than "hairy arg processor) debug name for its
    		own IR1-CONVERT-LAMBDA-BODY call
    	...(Check for analogous internal uses of debug-name-ish
    		stuff in GENERATE-OPTIONAL-DEFAULT-ENTRY, but there
    		are none.)
    	defined AS-DEBUG-NAME to support this
    William Harold Newman committed Jan 6, 2002
Commits on Jan 5, 2002
  1. 0.pre7.113:

    	minor tweaks while hunting bug 138...
    	...gave PREV-LINK a painfully explicitly mnemonic name
    William Harold Newman committed Jan 5, 2002
Commits on Jan 3, 2002
  1. 0.pre7.112:

    	more bug-138-related assertions and tweaking
    William Harold Newman committed Jan 3, 2002
Commits on Jan 2, 2002
  1. 0.pre7.111:

    	hunting bug 138...
    	...Poking around in the bug 138 test case, I found that the
    		failure is occurring for a LAMBDA which represents
    		the inline expansion of LAYOUT-INHERITS. It seems
    		correct for :INLINE LAMBDAs not to be in
    		COMPONENT-LAMBDAS, so it looks as though the bug is
    		in the AVER, not the code it's trying to protect,
    		so I added a new :INLINE case to the check logic.
    		Alas, that only converted bug 138a into bug 138b.
    	...added some assertions and comments hunting for 138b
    	redid DUMP-CODE-OBJECT loop for clarity as LOOP not DO
    William Harold Newman committed Jan 2, 2002
Commits on Jan 1, 2002
  1. 0.pre7.110:

    	added tests for DIRECTORY on hierarchical directories
    William Harold Newman committed Jan 1, 2002