Aaron.Sloman.XX@cs.bham.ac.uk (Aaron Sloman See text for reply address) writes:
> [To reply replace "Aaron.Sloman.XX" with "A.Sloman"]
>
>
> Marco Antoniotti <marcoxa@cs.nyu.edu> writes:
>
> > Date: 20 Nov 2000 12:30:13 -0500
> > Organization: New York University
> >
> > > E.g. suppose you create a directory ~/poplib, then in your login
> > > script do
> >
> > ...
> >
> > Thanks for the pointers. However it seems to me that you need to (at
> > least) re-link parto of the poplog "system-wide" directory locally to
> > do so.
>
> I don't know if anyone else has responded to this, but I don't
> really understand it.
>
> I had previously assumed that you had read enough of the
> instructions to work out how to start up Polog, so I didn't say
> anything about that in my answer to your question about startup
> files. Maybe I made a mistake and should have filled that in.
Yes. I believe I have an understanding of the way Poplog is set up.
> If that is what you are referring to then the answer is
>
> (a) define the environment variable $usepop to refer to the root
> directory in which Poplog is installed, e.g.
> /usr/local/poplog/v15.53/
>
> (The directory pop should be just below that).
>
> Then do this if you use csh or tcsh
> source $usepop/pop/com/poplog
>
> or, if you use sh, ksh, or bash, do
> . $usepop/pop/com/poplog.sh
Done that. It works like a charm.
>
> People who use poplog a great deal often put the definition of the
> environment variable and the source or "." command in their login
> files.
>
> The second command sets up various environment variables, alters
> your $PATH, etc.
>
> After that the following commands should work:
>
> pop11
> prolog
> (or, equivalently: pop11 +prolog)
> clisp
> (or pop11 +clisp)
> pml
> (or pop11 +pml)
> xved
>
> (see the other things linked to basepop11 in the directory
> $popsys, which is added to your $PATH).
They do.
> > AFAIU, I don't have the option of a "regular"
> >
> > ~/poplog-init
> >
> > file, do I?
>
> What would it do?
>
> The closest thing to this is
>
> $poplib/init.p
Copy that.
>
> If you don't define your own $poplib it defaults to ~, in which
> case the init file would be
>
> ~/init.p
>
> (and for lisp initialisation ~/init.lsp)
The problem is that I set up the poplog environment in a "shared"
location on my disk, and I want *both*
$poplib/init.{p,lsp,pl,pml}
and
~/init.{p,lsp,pl,pml}
where $poplib is the shared location. The two files may contain
different things. Elisp/Emacs, CLisp and CMUCL have this notion of
'site-init' and 'init file'.
For the time being it is not a problem (since I am the sole user), but
it may become a problem later on.
Anyway, this is minor.
> > 1 - DEFPACKAGE does not understand the :DOCUMENTATION option.
> > 2 - The COMPILE-FILE function should leave some trace on the file
> > system. This is just for "compatibility" with other systems.
> > Maybe the result of the compilation of "foo.lsp" could be a dummy
> > file like
> >
> > ;;; foo.pfs -- "Dummy" compilation file for 'foo.lsp'.
> > ;;; Poplog Common Lisp Version XXXXXXXX
> > (load "foo.lsp")
> >
> > This would help me port MK:DEFSYSTEM.
>
> John Williams at Sussex university built the Poplog Common Lisp
> system. However he is now employed to do other things, and may
> not respond to such requests.
He did.
I went through the sources. The DEFPACKAGE is very easy to fix. The
COMPILE-FILE a little more complex. Thanks for the instructions.
Anyway. It will take me some time. I have some pressing things to do now.
Cheers
--
Marco Antoniotti =============================================================
NYU Bioinformatics Group tel. +1 - 212 - 998 3488
719 Broadway 12th Floor fax +1 - 212 - 995 4122
New York, NY 10003, USA http://galt.mrl.nyu.edu/valis
Like DNA, such a language [Lisp] does not go out of style.
Paul Graham, ANSI Common Lisp
|