> Tim, if patches were made available that would allow Axiom to > transition to ANSI GCL would there be any chance they could be merged > in with the latest release branch? Or do we want to avoid dealing with > the problems that will surely crop up moving between Lisp > implementations until the proper rewrite is done?
there is a public arch archive for the sbcl port (see http://arch.axiom-developer.org). i know i'm back to the "bad tim" role but lets look at the issue of a "cheap and quick" port to ansi. does the port work in sbcl/clisp/other ansi? does the hyperdoc/graphics interface work? there are subtle points to check. for instance, the BOOT compiler spits out (functionp symbol) which i believe needs to become (fboundp symbol). a (functionp symbol) won't fail but it used to return T and now returns NIL thus taking a different code branch. is sbcl/clisp/other ansi building included in the makefiles? how do you handle system startup since *restart-hook* doesn't seem to be ansi? how do you handle shell variables (e.g. (|getEnv| "AXIOM")? the best case is to start patching the axiom--sbcl--1 branch and do A/B testing against the current axiom. that way many people can download and test the sbcl code without stomping on their main branch. t _______________________________________________ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer
