Common Lisp for Mac OS X
in [Lisp]
|
From: Marc Mientki on 27 May 2010 05:16 Hello, Which implementation of Common Lisp should I choose if I want to write applications for OS X? Thus created applications must have the look and feel of native Mac software. reagrds Marc PS. Sorry for my poor english!
From: Raffael Cavallaro on 27 May 2010 09:13 On 2010-05-27 05:16:44 -0400, Marc Mientki said: > Which implementation of Common Lisp should I choose if I want to write > applications for OS X? Thus created applications must have the look and > feel of native Mac software. Clozure Common Lisp, totally native look and feel, cocoa bridge, free, both 32 and 64 bit, ppc and intel: <http://trac.clozure.com/ccl> LispWorks Common Lisp, Native look and feel, cocoa bridge, cross platform gui toolkit, 32 & 64 bit, ppc and intel, paid with a free trial version: <http://www.lispworks.com/downloads/index.html> hth Ralph -- Raffael Cavallaro
From: Pascal J. Bourguignon on 27 May 2010 09:50 Raffael Cavallaro <raffaelcavallaro(a)pas.despam.s.il.vous.plait.mac.com> writes: > On 2010-05-27 05:16:44 -0400, Marc Mientki said: > >> Which implementation of Common Lisp should I choose if I want to >> write applications for OS X? Thus created applications must have the >> look and feel of native Mac software. > > Clozure Common Lisp, totally native look and feel, cocoa bridge, free, > both 32 and 64 bit, ppc and intel: > > <http://trac.clozure.com/ccl> > > LispWorks Common Lisp, Native look and feel, cocoa bridge, cross > platform gui toolkit, 32 & 64 bit, ppc and intel, paid with a free > trial version: > > <http://www.lispworks.com/downloads/index.html> However, if the OP plans to deploy his application on iPhone/iPod/iPad eventually, and to spread some FUD, I'll note that both these implementations unfortunately contain their own compiler, and therefore are forbidden AFAIUI by the EULA or whatever "agreement" Apple imposes on developers wanting to distribute applications for these platforms thru the AppStore. On the other hand, clisp would be compiled by Apple's gcc, so it would, formally, be closer to be acceptable by Apple. (Besides, I'd like to see a cocoa bridge in clisp, and I don't have the time to do it myself, so let's spread this FUD, if it helps motivate somebody to do it >:-} ). -- __Pascal Bourguignon__ http://www.informatimago.com
From: Raymond Toy on 27 May 2010 13:16 On 5/27/10 9:50 AM, Pascal J. Bourguignon wrote: > However, if the OP plans to deploy his application on iPhone/iPod/iPad > eventually, and to spread some FUD, I'll note that both these > implementations unfortunately contain their own compiler, and > therefore are forbidden AFAIUI by the EULA or whatever "agreement" > Apple imposes on developers wanting to distribute applications for > these platforms thru the AppStore. > > On the other hand, clisp would be compiled by Apple's gcc, so it > would, formally, be closer to be acceptable by Apple. (Besides, I'd But clisp has its own compiler, so if the presence of a compiler disqualifies an app, won't clisp be disqualified? Maybe not having a native-code compiler is enough? Ray
From: Pascal J. Bourguignon on 27 May 2010 13:25
Raymond Toy <toy.raymond(a)gmail.com> writes: > On 5/27/10 9:50 AM, Pascal J. Bourguignon wrote: >> However, if the OP plans to deploy his application on iPhone/iPod/iPad >> eventually, and to spread some FUD, I'll note that both these >> implementations unfortunately contain their own compiler, and >> therefore are forbidden AFAIUI by the EULA or whatever "agreement" >> Apple imposes on developers wanting to distribute applications for >> these platforms thru the AppStore. >> >> On the other hand, clisp would be compiled by Apple's gcc, so it >> would, formally, be closer to be acceptable by Apple. (Besides, I'd > > But clisp has its own compiler, so if the presence of a compiler > disqualifies an app, won't clisp be disqualified? Maybe not having a > native-code compiler is enough? Well, Apple's EULA is silly anyways, but specifically in the case of clisp, I would argue that it implements the "Interpreter pattern" in Objective-C (which is a superset of C). A VM interprets a sequence of small objects. -- __Pascal Bourguignon__ http://www.informatimago.com/ |