Hey gang! Now that 5.9.1 is out, I had a couple of questions about 5.9.2
a) Should Maximabook be split out of docs into its own cvs module? It's
getting rather large to be included by default now, and it's going to get
larger.
b) Should I wait to upload my changes until a) is decided? (I'd rather not
as that means my machine is a single point of failure, but I can understand
people not liking a couple extra megs in the cvs checkout)
c) How are we going to handle this phase of development? I know Jim is
working on merging a big cleanup patch (woo-hoo!) but I'm not clear how that
will work with the downcasing. Clearly we need some point at which
everything stops, we downcase and get working again, and then we accept new
patches to the downcased code. Essentially it would be silly to do a lot of
work on the codebase until we know how this is going to happen. Is the plan
to i) have some one person do the patch merging and preliminary downcase
work, then have the rest of us jump in ii) merge all outstanding patches to
date, then break up the downcasing among ourselves? iii) Something more
intelligent I haven't thought of?
Just for fun, I downcased all the lisp files in src/ and compiled them using
the lisp compile method and cmucl. Here were the results:
; Compilation unit finished.
; 11 errors
; 156 warnings
; 313 notes
All 11 errors were the same:
; Error: (during macroexpansion)
; Error in function MFORMAT-TRANSLATE-OPEN: Unknown format op.
So it looks like it might not be hard to at least compile a downcased Maxima,
although who knows what the test suite will do.
CY
P.S. - sorry if a couple duplicates of this show up - I was being a dork and
using the wrong identity to send the message.