porting Symbolics code to Common Lisp
Would this code be released under a free license? If so, a first step vould be to publish it as is, so that it may be audited for further consideration. An open source program could have an intrinsic interest that would motivate people to help porting it.
The effort to port it to Common Lisp would depend on:
- whether it's written in Zeta Lisp or in Common Lisp (or CLtL);
- the size of the code;
- its dependencies on Symbolics libraries and features, notably whether it has a GUI;
- the code quality (well structured and modular code is more easily ported than code mixing various level of abstraction including system or platform dependencies); etc.
There is also the option to run it in Genera http://www.symbolics-dks.com/ (actually the OpenGenera virtual machine), so you don't have to port it at all, if the purpose is only to have it run on MacOSX.
--
__Pascal Bourguignon__
Here’s a question for the active developers - I have some (Symbolics) Lisp code from mid-1980s. Since I still have two of the machines, I can run the code, but what should be my trajectory if I wanted to rewrite that code into something in a more current lisp? Say for a Mac Pro. Cost is not (necessarily) an object, since I would propose cost based on best solution. I haven’t actively developed (in Lisp or any other language) for 30 years, so it’s not a task I’d embark upon myself, but I’m curious to pose this proposition to others that have a love, respect and talent with the Lisp language. This thread caught my interest, since LW was something that seemed appropriate to consider, but for tinkering with code, is a bit prohibitive in cost.
-Jonathan Longcore
University of New Mexico
________________________________________
From: owner-lisp-hug@lispworks.com <owner-lisp-hug@lispworks.com> on behalf of Jean Bresson <Jean.Bresson@ircam.fr>
Sent: Saturday, May 7, 2016 1:39:27 PM
To: Laughing Water
Cc: Lisp Hug Lispworks
Subject: Re: Changes to delivery on Mac
I think I've had the same problem when upgrading to LW7.
The solution I got from lw-support was to use :STARTUP-BITMAP-FILE NIL in the delivery keywords.
(in other work, do not use a startup bitmap anymore if you did use one)
It fixed the problem in my case.
There were also a few missing items in the default application menu (Quit, Hide etc.) which I have had to insert myself.
JeanOn May 7, 2016, at 3:10 PM, Laughing Water <lw@mt.net> wrote:I’ve been poking around the documentation to find out why my delivery script that worked fine on LW Pro Mac 6 isn’t working on 7. Does anyone know offhand what might have changed?What I have succeeded in getting is a double-clickable app whose icon has a circle-slash symbol over it. When I run it my main window does not appear, and I get a menubar with a single menu that has my app name. The remaining menus, instead of being in the menubar, are available in a hierarchical menu item named "<<My Application’s Name>> application menus”..Laughing Water_______________________________________________Lisp Hug - the mailing list for LispWorks userslisp-hug@lispworks.comhttp://www.lispworks.com/support/lisp-hug.html_______________________________________________Lisp Hug - the mailing list for LispWorks userslisp-hug@lispworks.comhttp://www.lispworks.com/support/lisp-hug.html
_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html
_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html