Thread View: comp.lang.clos
3 messages
3 total messages
Started by Reed Little
Mon, 12 Oct 1992 20:09
clos & environment available?
Author: Reed Little
Date: Mon, 12 Oct 1992 20:09
Date: Mon, 12 Oct 1992 20:09
12 lines
1046 bytes
1046 bytes
i miss my symbolics. is there a clos implementation & development environment available for "standard" architectures (sparc & hp specifically) i need such things as a class examiner (like the symbolics flavor examiner), good debugger, network capability, multi-processes, good inter-process communication (both on the same box and other boxes on the network), and a file cm/cc system. thanks. ======================================================================== reed little software engineering institute - carnegie mellon university little@sei.cmu.edu, +1.412.268.5792
Re: clos & environment available?
Author: Clinton Hyde
Date: Tue, 13 Oct 1992 15:47
Date: Tue, 13 Oct 1992 15:47
44 lines
2271 bytes
2271 bytes
;;i miss my symbolics. is there a clos implementation & development ;;environment available for "standard" architectures (sparc & hp specifically) ;;i need such things as a class examiner (like the symbolics flavor examiner), ;;good debugger, network capability, multi-processes, good inter-process ;;communication (both on the same box and other boxes on the network), and ;;a file cm/cc system. thanks. is there a clos imp? yes, there are at least two. Lucid and Franz Inc. both have pretty good versions of CLOS. I use Franz' version. because of this, following answers apply only to it... class examiner: none that I know of. good debugger: well, it's not bad, but not the window debugger. I'm working on a window debugger that runs under CLIM (the version I have is for Lucid...which I can't test). network capability: not sure what you mean, but it is possible to do IPC/RPC sorts of things via sockets. multi-process: lightweight processes are there. i use them all the time. the startup stream is really more equivalent to the cold-load stream. ipc: i worked a project with this last year, using a third-party comm toolkit (ISIS). once ISIS settled down (it was prone to wedging until V3), it went pretty smoothly, for about 8 machines (incl two SGs). I don't know what "file cm/cc" is... whatever you get, it's not going to be Genera. Franz at least has decent link with Emacs/Epoch, which I use. that's about the closest to ZMACS as is possible. -- clint -- Clint Hyde "Give me a LispM or give me death!" -- anonymous Advanced Decision Systems/BAH Internet: chyde@chesapeake.ads.com 1953 Gallows Rd, Suite 600 Vienna, VA 22182-3934 (703) 902-7130
Re: clos & environment available?
Author: Martin Mikelsons
Date: Sat, 17 Oct 1992 00:09
Date: Sat, 17 Oct 1992 00:09
65 lines
3379 bytes
3379 bytes
;;Reed Little writes:
;;i miss my symbolics. is there a clos implementation & development
;;environment available for "standard" architectures (sparc & hp specifically)
;;i need such things as a class examiner (like the symbolics flavor examiner),
;;good debugger, network capability, multi-processes, good inter-process
;;communication (both on the same box and other boxes on the network), and
;;a file cm/cc system. thanks.
We all miss our Symbolics (even if we never worked with one). The concept
of window and mouse oriented programming tools integrated with the run-time
and the editing environment is without question a big winner. Symbolics
was a leader and inovator in the field. But Lisp on general-purpose
architectures has been catching up. Each of the major Lisp suppliers has
an entry in the field: Harlequin has Lispworks, Franz has Composer, and
Lucid has XLT. As the principal developer of one of these (XLT) I would
like to reply that we are attempting to satisfy Mr. Little's needs and
wishes.
XLT is a set of advanced Lisp an CLOS programming tools for Lucid Common
Lisp. It is becoming available on a variety of "standard" architectures,
including Sparc, RS6000, HP700/800 and Decsystem. It includes a range
of facilities which are (very briefly) mentioned below:
Run-Time Tools
Data Inspectors for all Common Lisp data types
Inspect and modify all components with simple
mouse gestures
CLOS Inspectors specially adapted to the OO world
Instance inspector to view and modify all slots
Class, Generic Function and Method viewers
Class Browser to show a graphic view of the class
hierarchy
Debugging Tools
Stack Inspector shows the call chain in one Lisp
sub-process, and allow various restart actions
Frame Inspector to view and modify arguments and
local variables
Visual Stepper
Source-Level Tools
Program Analyzer
Program Follower
Control Graph
Data Flow Graph
Class and Accessor usage
Defsys facility
Interface to GNU Emacs
Network connection provides a dynamic peer-to-peer interface
between Lucid Common Lisp and GNU Emacs
Emacs commands to fetch arglist, description, macroexpanded
form; send form(s) to be evaluated, compiled, inspected.
Mouse click in inspector can bring up source in
Emacs buffer.
As the developer of XLT, I may be somewhat biased when I claim that
Lisp environments on gp architectures have achieved most of the
functionality of their dedicated ancestors and rivals. In addition,
portability of code among a wide variety of platforms allows one to
exploit more effectively todays heterogenous networked computing
environment.
Sincerely, Martin Mikelsons <mm@lucid.com> (415)329-8400 x5533
Lucid, Inc., 707 Laurel Street, Menlo Park CA 94025
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads