[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Nov 20 12:30:13 2000 
Subject:Re: Init files?!? 
From:Marco Antoniotti 
Volume-ID:1001120.01 

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:


> > I have a question regarding "init files" (I know I should have RTFMed
> > a little more, but I am notoriously lazy).
> 
> It's often much quicker to get help from an experienced user,
> especially when the documentation, though very rich, is hard for a
> beginner to navigate. See HELP helpfiles
>     $usepop/pop/help/helpfiles
>     $usepop/pop/lisp/help/helpfiles
>     $usepop/pop/lisp/ref/poplog_only
>         (Summarises poplog-specific features of Poplog common lisp)
> 
>     http://www.cs.bham.ac.uk/research/poplog/doc/lisphelp/bugs
>         This summarises missing/incomplete features of Poplog
>         Common Lisp, relative to ANSI lisp.
> 
> Anyhow, here's an answer to your question if I have understood it.
> 
> Either in your login file, or just before you use start up poplog
> define the unix environment variable $poplib to have as its value
> the name of a directory in which you want to put initialisation
> files for pop-11, Ved, poplog prolog, poplog common lisp, or poplog
> ML. If you don't do this it defaults to your login directory,
> which is not what most people want.
> 
> 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.

AFAIU, I don't have the option of a "regular"

	~/poplog-init

file, do I?

> best read in Ved alas because someone converted it to use Ved's
> "fancy" graphic characters.)
> 
> 
> You may also find HELP poplisp useful in case you need to invoke any
> pop-11 (or Ved) utilities from Lisp.
> 
> I am not a lisp user, so I may have forgotten some crucial detail!
> 
> A (partly out of date/incomplete) overview of the poplog directory
> tree can be found in
>     $usepop/pop/doc/sysspec
> 
> Any numbers in there will definitely be out of date (memory, disk,
> CPU times , etc.)
> 
> Hope that helps.

It does, thanks.

> 
> If you develop any libraries, etc. that work with Poplog common
> lisp, and you would like to make them available at the FreePoplog
> site, or would like pointers to them to be included in the existing
> information files, let me know.

I am trying out the system on a number of simple libraries and tools I
am maintaining.

I already noted a few things that might be easy to fix.

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.

As per other libraires, the first one I tried is a simple
implementation of the UNION-FIND algorithms and data structures.  It
works nicely under Poplog CL.  It is part of the CLOCC and it is
released under the LGPL.  This (and other ones) can definitively be
part of the FreePoplog site.

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