From: Sam S. <sd...@gn...> - 2005-02-24 16:44:40
|
> * Bruno Haible <oe...@py...t> [2005-02-24 16:58:59 +0100]: > > Sam wrote: >> >> clisp.exe has certain directories built-in. >> >> >> > clisp.exe could take the current run-time path? >> >> how? >> >> getexecname() is not standard. > > Woe32 has GetModuleFileName. > > char location[1000]; > GetModuleFileName(NULL,location,sizeof(location)) > > retrieves the path name of the running executable. yes, I know. I even thought that this might make the clisp driver unnecessary: all it is used for is: -B/-M defaults -- can be extracted from exec filename (use -M "" for bootstrap) -K - obsoleted by dynamic modules /usr/bin/clisp is just a symlink to /usr/lib/clisp/base/lisp.run (and find_executable() actually calls realpath() so this is not a problem) -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.iris.org.il> <http://www.camera.org> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://pmw.org.il/> There's always free cheese in a mouse trap. |