From: Marco A. <ma...@cs...> - 2004-01-07 18:00:08
|
The best way to deal with old software like this looks like to be, is to write a MK:DEFSYSTEM or an ASDF file for it and take it from there. It will give you an understanding of the code structure and it will give you something better and portable to work with. Cheers Marco On Monday, Jan 5, 2004, at 13:41 America/New_York, kr wrote: > i am trying to compile okbc > ( http://www.ai.sri.com/~okbc/ ) > on sbcl-0.8.0, and quite some porting is needed. > > the problem i am running into right now is that i need the > corresponding variable in sbcl for the following: > > (defun current-source-file () > #+Lucid lcl::*source-pathname* > #+ALLEGRO excl::*source-pathname* > #+MCL ccl::*loading-file-source-file* > #+Harlequin-Common-Lisp dspec:*source-pathname* > #-(or Lucid Allegro MCL Harlequin-Common-Lisp :SBCL) > (generic-error "Implement me")) > > i wonder whether sbcl has something like this. searching for the most > obvious terms using apropos did not bring up the right variable for me. > > -- > regards > markus krummenacker > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Sbcl-devel mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-devel > -- Marco Antoniotti http://bioinformatics.nyu.edu NYU Courant Bioinformatics Group tel. +1 - 212 - 998 3488 715 Broadway 10th FL fax. +1 - 212 - 998 3484 New York, NY, 10003, U.S.A. |