HDTenEightyP/NetNews huggingface dataset:
From: cote@cs.ucsd.edu (Brad Cote)
Newsgroups: comp.lang.lisp
Subject: Re: How can I run INTERLISP?
Keywords: interlisp
Date: 9 Sep 92 23:04:54 GMT

inglehar@bert.eecs.uic.edu (James Inglehart) writes:

>I have a 1977 INTERLISP program, written at Stanford, and originally
>run under TOPS-20 at the Xerox PARC facility. (Its author has suggested
>to me that it may still run under "Xerox Lisp.")

Try to find a Xerox 1108 type (Dandilion) workstation at your
university. There might be one gathering dust somewhere. The
development environment is very, very good. It is a very interesting
machine in its own right, but the software environment is still
years ahead of any Unix/C development environment today (including all
the X stuff I've used).

>I need to get this 3500-line program running as painlessly and rapidly
>as possible. (I don't know INTERLISP, or any other Lisp, for that
>matter.) What should I do? Here at the University of Illinois at
>Chicago we have Stanford Lisp on the mainframe, but the program won't
>run under it. Can any one suggest a compiler/interpreter I can access
>through the net that will understand this program?

>Should I resign myself to learning Lisp and translating this old program
>into some more modern dialect (GNULisp, for example)? This could take me
>a month or more. But I must get this program running.

You might have a problem with Interlisp. It is not lexically scoped, which
means that a function can access a variable in a calling funtion. Most
*good* software I saw in Interlisp did not do this, but if it was
developed by grad students, you never know...

All the modern Lisp's (Scheme, Franz, Common) all have lexical scoping.
There is no common function library for Lisp. The language is very
simple in syntax, but relies very heavily on built in functions in
the language. Before Common Lisp, there was no defined library
fuctionality. I think that finding a machine translator is almost
out of the question, and hand translation will be very tedious. I suggest
recoding the program from a functional description, using the old
code as a guide. You will find that it will be much easier to use a
newer Lisp, rather than C. The code size for a C implementation could
be as much as three times as large.

>Any advice from experienced Lisp programmers will be greatly appreciated.
>Please contact me directly at inglehar@bert.eecs.uic.edu. Thank you.


>James Inglehart
				
				Brad Cote' (ex Xerox and Symbolics programmer)
				University of California, San Diego
				STARE Project
Newsgroups: comp.lang.lisp
From: haltraet@monsun.si.no (Hallvard Tr{tteberg)
Subject: changing the pathname type
Date: Mon, 14 Sep 1992 08:12:47 GMT
Organization: Center for Industrial Research, Dept. of Knowledge Based Systems

Hi Lispers,

I have a quite trivial problem, which I cannot find the information to
solve.

I would like to change the filetype of a pathname (e.g. to nil
(unspecified) or .lisp). There is no (setf pathname-type) in my lisp,
nor is it mentioned in CLtL, although pathname-type is called an
accessor. I cannot use (merge-pathnames <filename> ".lisp") since this
will only "change" the pathname-type if it is nil (unspecified). I
cannot merge the other way, i.e. (merge-pathnames ".lisp" <filename>)
since I would like to use nil (unspecified) instead of ".lisp". I want
to avoid doing string-search since it would likely be non-portable.

Regards, Hallvard
--
Hallvard Traetteberg
Dept. of Knowledge Based Systems
Center for Industrial Research
Box 124 Blindern, 0314 Oslo 3
NORWAY

Tlf: +47 2 45 29 83 or  +47 2 45 20 10
Fax: +47 2 45 20 40
Email: Hallvard.Tretteberg@si.no
From: so@CS.WISC.EDU (Bryan S. So)
Newsgroups: comp.lang.lisp
Subject: copy-array?
Date: 14 Sep 92 22:12:47 GMT

This is almost the first time I seriously use arrays
in Common Lisp.  Now, how come there is no intrinsic
function to make a copy of an array?

The only algorithm I have is to make a new array then
assign the elements one by one.  Is there an easier/
more efficient method to do this?

Thanks.


Bryan So (so@cs.wisc.edu)
Newsgroups: comp.lang.lisp
From: york@oakland-hills.lucid.com (Bill York)
Subject: Re: changing the pathname type
Reply-To: York@Lucid.COM
Organization: Lucid, Inc.
Date: 14 Sep 92 11:12:44

In article <HALTRAET.92Sep14091247@monsun.si.no> haltraet@monsun.si.no (Hallvard Tr{tteberg) writes:

   I would like to change the filetype of a pathname (e.g. to nil
   (unspecified) or .lisp). There is no (setf pathname-type) in my lisp,
   nor is it mentioned in CLtL, although pathname-type is called an
   accessor. I cannot use (merge-pathnames <filename> ".lisp") since this
   will only "change" the pathname-type if it is nil (unspecified). I
   cannot merge the other way, i.e. (merge-pathnames ".lisp" <filename>)
   since I would like to use nil (unspecified) instead of ".lisp". I want
   to avoid doing string-search since it would likely be non-portable.

You can use make-pathname, specifying the type explicitly and
defaulting everything else from the original pathname.

> (make-pathname :type nil :defaults #P"/foo/bar.lisp")
#P"/foo/bar"
> (pathname-type *)
NIL
>
From: danny@farallon.com (Danny Brewer)
Newsgroups: comp.lang.lisp
Subject: Re: copy-array?
Date: 15 Sep 92 14:00:36 GMT
Followup-To: comp.lang.lisp
Organization: Farallon Computing, Inc.

In article <9209142212.AA24213@brownie.cs.wisc.edu>, so@CS.WISC.EDU (Bryan
S. So) wrote:
> 
> The only algorithm I have is to make a new array then
> assign the elements one by one.  Is there an easier/
> more efficient method to do this?
> 

That's what I concluded myself.  I wrote the following
function which makes a new array and copies the elements
of the old array into it.  I use two temporary vectors
displaced to the arrays so that I treat the copy like
a sequence.

About a year ago this question of copying arrays came
up and I posted this code.  Someone suggested that I
use REPLACE instead of DOTIMES because it might be
more efficient.  I tried this which resulted in more
than doubling the speed.  If you pass in a copier
function, then the DOTIMES method is used so that
the copier function can process each element.


(DEFUN Copy-Array (array &KEY copierFn)
  "Make a new array which is a copy of the original."
  (LET* (
         (arrayType (ARRAY-ELEMENT-TYPE array))
         (arraySize (ARRAY-TOTAL-SIZE array))
         (newArray (MAKE-ARRAY (ARRAY-DIMENSIONS array)
                               :ELEMENT-TYPE arrayType
                               :ADJUSTABLE (ADJUSTABLE-ARRAY-P array)))
         (source (MAKE-ARRAY arraySize
                             :ELEMENT-TYPE arrayType
                             :DISPLACED-TO array))
         (dest (MAKE-ARRAY arraySize
                           :ELEMENT-TYPE arrayType
                           :DISPLACED-TO newArray))
         )
    (IF copierFn
      (DOTIMES (i arraySize)
        (SETF (ELT dest i) (FUNCALL copierFn (ELT source i))))

      ;; If no copierFn was supplied, then use REPLACE
      ;;  because the compiler might generate much more
      ;;  efficient code for it.
      (REPLACE dest source))
    newArray))


Sorry I didn't use dashes in the variable names, but I
wrote this a long time ago.

Danny Brewer
danny@farallon.com
From: simon@lia.di.epfl.ch (Simon Leinen)
Newsgroups: comp.lang.lisp
Subject: Re: (ed), CLX, and OpenWindows
Date: 11 Sep 92 11:20:18 GMT
Organization: DI-LIA -- Ecole Polytechnique Federale de Lausanne
In-reply-to: gjw@csis.dit.csiro.au's message of 11 Sep 92 06:28:47 GMT
X-Md4-Signature: 8a5d62ad5ac0d861223c75aff6a34713

In article <1992Sep11.062847.11139@csis.dit.csiro.au>
gjw@csis.dit.csiro.au (Graham Williams) writes:

   Short of asking OpenWindows not to use the xauthority security
   mechanism, how can I convince OpenWindows that the editor is
   authorised!

You can solve this problem by upgrading to the latest CLX release
(contrib/CLX.R5.02 on export) which supports xauth-based access
control.
-- 
Simon.
Xref: sparky comp.lang.lisp:2374 comp.sys.next.software:1467
From: bcs@waikato.ac.nz
Newsgroups: comp.lang.lisp,comp.sys.next.software
Subject: Summary: free CL + CLOS?
Date: 6 Sep 92 16:11:28 +1200
Organization: University of Waikato, Hamilton, New Zealand

Thanx to all who responded to my queries for a Common Lisp with CLOS, the
net wins out again over all conventional reference sources 8-)

Summary:

Many people pointed me towards pcl as a reliable CLOS implementation
(conformance was questioned by a couple of people), which might/might be
made to/definately does run under akcl.

Glen Diener (grd@ccrma.Stanford.EDU)
Sandra Loosemore (loosemore-sandra@CS.YALE.EDU)
Tim Bradshaw <tim.bradshaw@edinburgh.ac.uk>
Barry Margolin <barmar@Think.COM>
Jim Levins (jblevins@uniwa.uwa.edu.au)
Bill Vrotney (bvrotney@ads.com)
Trent Lange (lange@CS.UCLA.EDU)
Jake ? (jake@skatter.usask.ca)
Bill ? (bil@ccrma.Stanford.EDU)

Many of these people also extolled the virtues (robustness, speed, fine
error checking) of the CMU CL system, which apparently uses pcl itself, as
did ted@NMSU.Edu.  The vote seems to be with this system (CMU CL) by quite
some margin, but...

I actually wanted a system for NeXT workstations, and in one of the two
queries I even remembered to say so!

Gregory Lampshire (gbol@orion.async.vt.edu) and k (asd@sage.cc.purdue.edu)
both pointed out that there is a ready-to-run image of akcl 615 + pcl in
the NeXT archives, and so there is:

sonata.cc.purdue.edu:/pub/next/submissions/akcl-615-pcl-image.{README,tar.Z}

I have uplifted this, but not yet tried it.  Am actually a bit nervous
about the NeXT community's habit of supplying binaries on the archives.
It's not as if NeXT are planning to unbundle the compiler like some I might
mention....are they?

Important quotes: (names omitted to protect the innocent)
----------------
|The CMU CL group has decided that it would not make sense to port CMU CL to
|the NeXT. If you complain to them (email slisp@cs.cmu.edu) it would be one
|more reason why they were wrong about this.

|AKCL does run under NeXTstep 2.0 and 3.0 (a patch is needed to run under
|3.0). You can get CLOS at parcftp.xerox.com /pub/pcl = latest pcls.  I
|compiled the latest PCL under AKCL NeXTstep 2.0 and it ran fine, the same
|should be true of NeXTstep 3.0 since PCL (CLOS) is written in pure Common
|Lisp.

|The file parcftp.xerox.com:/pub/pcl/March-92-systems.tar.Z
|contains the systems PCL (March 92 3a), CLCS, CLX (X11R5),
|and an inspecter.  The top level directory in this file
|contains a defsystem facility that can load everything.
|All you need to do is load the file "systems.lisp".
|The top level directory also contains a makefile for akcl. 
|You need to edit the first few lines of the makefile before    
|using it.

Thanx once more people,

+-Brent Summers, U of Waikato, NZ----------------------------------------+
|    "Laugh and the world ignores you.  Crying doesn't help either."     |
|      All opinions expressed are, of course, solely my own errors.      |
+------------------------------------------------------bcs@waikato.ac.nz-+
Newsgroups: comp.lang.lisp,comp.lang.lisp.franz,comp.unix.bsd
From: martyn@garfield.cs.mun.ca (Martyn Quigley)
Subject: Re: Franz Lisp lives!
Organization: CS Dept., Memorial University of Newfoundland
Date: Thu, 10 Sep 1992 02:52:42 GMT

jeff@aiai.ed.ac.uk (Jeff Dalton) writes:

>I have a compile-to-C version of Liszt that I developed a number of
>years ago and (together with some other people) I've recently made
>Franz Lisp work in 386BSD.  So, although I don't have time to do it
>myself right now, this version of Franz should be fairly easy to
>port to Sparcs and to random "Berkeley Unix" machines in general.
>If there is any interest in this, I will try to make the sources
>available fairly soon.
>-- jd

Yes please, yes please.

Martyn
From: SWM@stony-brook.scrc.symbolics.com (Scott McKay)
Newsgroups: comp.lang.lisp
Subject: Re: copy-array?
Date: 15 Sep 92 18:29:48 GMT
Organization: LCS news/mail gateway
X-Unparseable-Date: Tue


    Date: Tue, 15 Sep 1992 13:13 EDT
    From: Barry Margolin <barmar@think.com>

    In article <19920915145558.5.SWM@SUMMER.SCRC.Symbolics.COM> SWM@stony-brook.scrc.symbolics.com (Scott McKay) writes:
    >A "shame" is an understatement.  I think that, at the very least, this
    >correction to MAKE-ARRAY should be proposed during the dpANS public
    >review period.  

    Please do so.

    >		 (Note that I do not consider this a true correction of
    >an error of omission, not simply an extension.)

    If it's "not ... a ... correction", and "not ... an extension", what is
    it?  Or was the first "do not" an error?

Typo.  Sorry.

    I'd consider this an extension.  Our charter was to clarify the language
    as specified in CLtL, and add a condition system, iteration facility,
    and OO system.  We didn't limit ourselves strictly to this, but we tried
    not to go overboard.  I'm not saying that this particular feature is a bad
    idea, but since it adds to the language as specified in CLtL, strictly
    speaking it's an extension.
    -- 
    Barry Margolin
    System Manager, Thinking Machines Corp.

    barmar@think.com          {uunet,harvard}!think!barmar
Newsgroups: comp.lang.lisp
From: travt@cs.curtin.edu.au (Tony Travers)
Subject: Re: xit
Keywords: xit clue lcl
Organization: Curtin University of Technology
Date: Tue, 15 Sep 1992 08:25:51 GMT

hi

	please disregard the previous article 

	
	it involve having the wrong version of lcl


				thanks
					Tony
From: jl3j+@andrew.cmu.edu (John Robert Leavitt)
Newsgroups: comp.lang.lisp
Subject: Metering for Lucid 4
Date: 4 Sep 92 21:15:03 GMT
Organization: Center for Machine Translation, Carnegie Mellon, Pittsburgh, PA

Has anyone adapted Mark Kantrowitz's (mkant@cs.cmu.edu) metering package
to correctly take into account ephemeral bytes when it reports consing under
Lucid 4?  The current version only counts dynamic consed and there are times
when I don't want to test everything using (with-egc-off ...) wrapping.

-John.

-John R. R. Leavitt-----------------------------------------------------------
-Center for Machine Translation                                  412/268-2292-
-Carnegie Mellon University                                   jrrl@cs.cmu.edu-
------------------------------------------------------------------------------
From: tar@ISI.EDU (Thomas A. Russ)
Newsgroups: comp.lang.lisp
Subject: Re: changing the pathname type
Date: 14 Sep 92 16:54:05 GMT
Reply-To: tar@isi.edu
Organization: USC-ISI
In-reply-to: haltraet@monsun.si.no's message of 14 Sep 92 08:12:47 GMT


Well, there's always:

(make-pathname :host (pathname-host old-pathname)
	       :directory (pathname-directory old-pathname)
		...
		:type nil)
--

Thomas A. Russ                                             tar@isi.edu    
USC/ISI, 4676 Admiralty Way, Marina del Rey, CA 90292      (310) 822-1511
From: gadbois@mcc.com (David Gadbois)
Newsgroups: comp.lang.lisp
Subject: Re: Function to print in #S format
Date: 8 Sep 1992 19:40:34 -0500
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

    Date: Tue, 8 Sep 1992 15:19 CDT
    From: sjameson@fergie.dnet.ge.com (Stephen M Jameson)

    This ought to be a FAQ, but I haven't seen it.  How do I print a
    structure in #S-format, i.e. so that the reader will automatically
    reconstruct the structure?  The application is obvious: I would like
    to have a :PRINT-FUNCTION specified in the DEFSTRUCT which will
    print in a concise, non-readable format if a certain switch is set,
    and print in the verbose, readable format if the switch is not set.
    On the Symbolics I figured out a way to do it but it did not seem
    portable, and CLTL2 doesn't mention anything beyond the semantics of
    #S format, and that if you don't specify a :PRINT-FUNCTION, "a
    function is provided for the structure which will print out all its
    slots using #S syntax."

If you have CLOS hooked in, you can define a method on PRINT-OBJECT that
checks your switch (which probably should be just *PRINT-READABLY*) and
calls CALL-NEXT-METHOD if it is not set.  I do this so often I have
written a macro to deal with it:

(defmacro define-print-method ((object-var object-type stream-var) &body body)
  `(defmethod print-object ((,object-var ,object-type) ,stream-var)
     (if *print-readably*
	 #+Genera
	 ;; The default structure printer checks this and calls
	 ;; PRINT-UNREADABLE-OBJECT if it is not set.
	 (let ((scl:*print-structure-contents* t))
	   (call-next-method))
	 #-Genera
	 (call-next-method)
	 (print-unreadable-object (,object-var ,stream-var :type t)
	   ,@body))))

Note that CMU CL v15 did not let you use structure types as
specializers, so this will not work there.  I have not checked v16 yet
to see if they have fixed it.  For Lucid 4.0.x, you have to define
*PRINT-READABLY* and PRINT-UNREADABLE-OBJECT yourself.  At least Allegro
and MCL get it right without extra kludgery.  I sure will be happy when
the draft proposed CL standard gets accepted so I'll never have to worry
about portability problems again :-).

If you do not have CLOS, you can always how the structure's print
function do the #S printing by hand, but that is pretty gross.  Or you
could use implementation dependent accessors to get at the slot names
and values (this is in the FAQ) and write a general printer.

--David Gadbois
From: sjameson@fergie.dnet.ge.com (Stephen M Jameson)
Newsgroups: comp.lang.lisp
Subject: Re: Function to print in #S format
Date: 9 Sep 92 21:04:51 GMT
	<1992Sep9.011022.14516@jpl-devvax.jpl.nasa.gov>
Reply-To: sjameson@atl.ge.com
Followup-To: comp.lang.lisp
Organization: General Electric Advanced Technology Labs

In article <1992Sep9.011022.14516@jpl-devvax.jpl.nasa.gov> charest@Aig.Jpl.Nasa.Gov (Len Charest) writes:

>
>3. (mutually exclusive) Use CLOS. Ha Ha only serious.
>..................................................
>                                  Len Charest, Jr.
>                 JPL Artificial Intelligence Group
>                          charest@aig.jpl.nasa.gov

The problem here is that the CLOS standard requires no default readable
printing method, and the two implementations to which I have access (Allegro
4.1 and Genera 8.1.1) do not provide any.  In fact, I am not sure that one can
portably define (without implementation conditionals) a readable print-function
for a CLOS object.  If you set *print-readably* to T, then try to create CLOS
objects or define classes (from the command line), you get errors.  I know
there are ways to do what I am trying to do.  What I want to know is whether
there are easy ways.

--
Steve Jameson                           General Electric Aerospace 
sjameson@atl.ge.com                     Advanced Technology Laboratories
                                        Moorestown, New Jersey              
****************************************************************************
**  . . . but I do not love the sword for its sharpness, nor the arrow    **
**  for its swiftness, nor the warrior for his glory.  I love only that   **
**  which they defend . . .                                               **
**    -- Faramir, "The Two Towers"                                        **
****************************************************************************
From: wee@cs.ucdavis.edu (Chris Wee)
Newsgroups: comp.lang.lisp
Subject: Re: Freezing a variable: how?
Date: 6 Sep 92 18:58:06 GMT
Reply-To: wee@cs.ucdavis.edu
Organization: Computer Science, University of California at Davis.

I'm trying to help a prof. set up an EPROS system for a class.
Can someone point me to an ftp site that has the following lisp
for Sun Sparcs or Decstation 5000s (MIPS). I checked the standard
distribution for franz and it was available on for VAXen or Sun-3s.

Please email as I do not read this group regularly.

Thanks in advance.

COMPILING AND INSTALLING EPROS
==============================

1) You NEED:
        * A C compiler.
        * A Franz Lisp environment which includes:
            - An interpreter (lisp, at least version Opus 38.22).
            - A compiler (liszt, at least version 8.08 [.22]).


---
-chris

Newsgroups: comp.lang.lisp
From: gjw@csis.dit.csiro.au (Graham Williams)
Subject: (ed), CLX, and OpenWindows
Reply-To: gjw@csis.dit.csiro.au
Organization: Spatial Information Systems, CSIRO, Canberra, Australia
Date: Fri, 11 Sep 1992 06:28:47 GMT

In Lucid Common Lisp and CMU Common Lisp, for example, when running
under X11 I have things configured to run the supplied X11 Window based
editor when (ed) is called (both implemented, I presume, using CLX).  This
works fine under straight X11R4.  Under OpenWindows, with the default
usage of xauthority rather than xhost, I get the following
authorization error:

	Connection failure to X11.0 server unix display 0: Internal error
	during connection authorization check

	(xlib::x-error xlib:connection-failure :major-version 11 
	:minor-version ...)

Short of asking OpenWindows not to use the xauthority security
mechanism, how can I convince OpenWindows that the editor is
authorised!

I've checked the FAQ!

Thanks
---
Graham.Williams@csis.dit.csiro.au           ,--_|\   Tel: +61 6 275 0963
Spatial Information Systems, CSIRO-DIT     /      \  Fax: +61 6 257 1052
Australian National University, Canberra   \_.--_*/  GPO Box 664 ACT 2601
                                                 v

Newsgroups: comp.lang.lisp,comp.windows.x,comp.unix.aix
From: lugowski@ils.nwu.edu (Marek Lugowski)
Subject: lisp & digital video under X? (Sparc/RS 6000)
Summary: query about video and lisp under X; digital video for RS 6000?
Keywords: lisp X RS6000 dvi video Sparc
Organization: The Institute for the Learning Sciences
Date: Thu, 10 Sep 1992 23:20:30 GMT

(this is crossposted to comp.lang.lisp
			comp.windows.x
			comp.unix.aix)

I am seeking information on how various Lisps do, or can be made to
handle, video input under X windows, preferrably X11R5, but others,
too.  The video in question would ideally be a digitized (compressed)
signal stored on hard disk or other mass storage.  If digitized video
is not available, perhaps some analog video medium is.  We want to
play back canned video clips, about an hour's worth altogether under X
on the same screen as the rest of the interface.

The platforms involved are Sparc and (especially) RS 6000 but others
may be of interest.  Incidentally, any informed rumors on RS 6000
video are especially sought.

This information is sought for porting to X and expanding a sizable
AI/multimedia interface project already running under Macintosh Common
Lisp.

				-- Marek

Marek Lugowski                                          708/467-1872: voice
Institute for the Learning Sciences                     708/491-5258: fax
Northwestern University
1890 Maple Avenue
Evanston, IL 60201

lugowski@ils.nwu.edu

Xref: sparky comp.lang.lisp:2419 news.answers:2882
From: mdcutts@zion (Matthew Cutts)
Newsgroups: comp.lang.lisp
Subject: Lispview command to initialize window
Date: 10 Sep 92 18:08:26 GMT
Organization: The Great Beyond

Pardon if this is a silly question:
  I've been using Sun's Devguide to create a GUI, then the glv program to port  
it to Lispview code.  If I want to call up a popup window ("template window")  
that is defined under the class of the main window (let's call it "basetool"),  
what command would I use?
(make-instance 'basetool) works to initialize the main window, but I can't  
uncover how to pop up the template window.  Any advice would be appreciated,
even if it's setting me straight on terms.  Please reply directly via e-mail.
Thanks, Matt Cutts
mdcutts@ukpr.uky.edu
From: jeff@aiai.ed.ac.uk (Jeff Dalton)
Newsgroups: comp.lang.lisp,comp.lang.lisp.franz,comp.unix.bsd
Subject: Re: Franz Lisp lives!
Date: 11 Sep 92 14:34:20 GMT
Organization: AIAI, University of Edinburgh, Scotland

In article <16899@ucdavis.ucdavis.edu> mock@madrone.eecs.ucdavis.edu (Kenrick Mock) writes:
>The author of "PC-Lisp" for MS-DOS machines also has C source code
>available.

Does it include a Lisp compiler that produces code that works on a
386 or SPARC?

To go from zero Franz Lisps to two would be pretty amazing.

-- jd
Newsgroups: comp.lang.lisp