From: Craig B. <cr...@re...> - 2000-06-07 18:14:18
|
First, I wanna let you know that I built 0.6.5 on linux using sbcl-0.6.4. I haven't tried building with CMUCL on that platform yet. I'm trying to get multi-proc suport back in, and am making some progress. I have a few questions tho. Would there be any issues with having the stem loader just compile files that have changed source since the last time they were compiled. Have that turned on an off by a switch, so that we can still get clean builds. Maybe it could be more sophisticated and compile every file after the first changed file it finds in the stem list. I am still trying to work out the whole build process, so I may be suggesting something impossible. In general, I'm looking for ways to break the build process down a little bit so that my work in fixing MP is a little quicker. Right now it takes a good chunk of time to compile and load everything up till multi-proc.lisp only to find another problem. Then I gotta do it all over against when I fix it. Any suggestions would be welcome. When are def!struct and other def!<blah> constructs needed, and when are they not. Do I need to convert the defstructs in multi-proc.lisp to them? Is there any problem with breaking multi-proc.lisp into multiple files? One for processes, another for stacks groups. Thanx for SBCL! -- Craig Brozefsky <cr...@re...> Lisp Web Dev List http://www.red-bean.com/lispweb --- The only good lisper is a coding lisper. --- |