Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!princeton!mind!eliot
From: eliot@mind.UUCP
Newsgroups: comp.sys.mac,comp.lang.lisp
Subject: Re: Coral/Franz Extended Common Lisp PRESS RELEASE
Message-ID: <1189@mind.UUCP>
Date: Fri, 28-Aug-87 02:39:24 EDT
Article-I.D.: mind.1189
Posted: Fri Aug 28 02:39:24 1987
Date-Received: Sat, 29-Aug-87 16:09:03 EDT
References: <334@su-russell.ARPA> <1563@apple.UUCP> <3700@sdcsvax.UCSD.EDU> <1367@bloom-beacon.MIT.EDU>
Reply-To: eliot@mind.UUCP (Eliot Handleman)
Organization: Cognitive Science, Princeton University
Lines: 19
Keywords: Franz, debugging, X, foreign-coded functions
Xref: utgpu comp.sys.mac:5418 comp.lang.lisp:387
Summary: Bugs in Franz

I've been working with Franz Lisp on a Minivax 2 over the past year and
I'm wondering if any other users have noted difficulties - or bugs -
in the following not unsignificant areas:
1. the debugger, when called in the break loop, doesn't access the stack
   and so is entirely useless. (It does work if inserted somewhere within a
   function definition but that makes it tedious to use.) Wilensky's book
   makes it clear that this ought not to be the case. Not being inclined
   to perform the hack, I tried recompiling a later version of fixit.l
   that we got with a couple of RT's, but I got an error msg after the gc
   (and of course the package is useless unless compiled). Any ideas?

2. Similar problems with step.l, which doesn't do what the manual claims
  it should, unless inserted in a fn def.

Besides this, I was wondering if there is an X interface for franz around?
And generally passing lispvals to c routines? I've done this, but it only
works in limited contexts - now I can't be alone in this.

Thanks for all replies -