Re: Common LISP Implementations for Mac OS X?

From: Raffael Cavallaro (raffaelcavallaro_at_pas-d'espam-s'il-vous-plait-dot-mac.com)
Date: 03/10/05

  • Next message: Ulrich Hobelmann: "[OT] PostLisp, a language experiment" 
    Date: Thu, 10 Mar 2005 01:48:12 -0500

    In article <1110383386.875578.118530@f14g2000cwb.googlegroups.com>,
     "Alexander Repenning" <ralex@cs.colorado.edu> wrote:

    > MCL is our choice. Nice IDE, fast compiler, fast runtime (runs our
    > OpenGL stuff very fast), has an ephemeral garbage collector (essential
    > for continuously animated stuff). Not free, but you get what you pay
    > for. Distant second: LispWorks: generic - non OS X - interface, good
    > for cross platform development.

    Note that both Rainer Joswig and I have exactly the opposite ranking.
    This reflects our desire for a Mac OS X lisp that interfaces well with
    Cocoa, while your preference for MCL reflects your desire for a Mac OS X
    lisp that interfaces well with Carbon, understandable as you have a very
    large body of Carbon compatible legacy code.

    I think it would be fair to both MCL and LispWorks, as well as useful to
    newcomers to both, to state that MCL is the undisputed king of Carbon
    based Mac OS X common lisp implementations, while LispWorks is the clear
    choice (for now) if one wants easy access to Cocoa. This latter could
    change as OpenMCL progresses, however.

    BTW, while it is true that CAPI is a "generic - non OS X - interface,"
    Mac OS X users of LispWorks are not limited to CAPI - you can load
    Interface Builder nib files, and create any Cocoa UI you want. If you
    want a true Mac OS X Coca UI with LispWorks, you have to build it
    yourself - but this is not so different than MCL, where you use MCL's
    CLOSified Carbon calls to do the same thing that a LispWorks user
    accomplishes with Lispworks objc package interfacing with Cocoa.

    regards

  • Next message: Ulrich Hobelmann: "[OT] PostLisp, a language experiment"

    Relevant Pages

    • Re: Help choosing Lisp for Mac OSX
      ... > Cocoa versus Carbon: there is no Cocoa or Carbon GUI. ... been available for a couple of years, while MCL has been in use by Mac ... Since you've seen fit to dis every other Mac OS X lisp other than MCL, ...
      (comp.lang.lisp)
    • Re: Common LISP Implementations for Mac OS X?
      ... >> For me MCL is not a Mac OS X Lisp. ... Actually I think LispWorks is much better than MCL. ... enabling people to write Carbon-based Mac OS X applications. ...
      (comp.lang.lisp)
    • Re: Comments on MCL vs LispWorks for OS X ?
      ... LispWorks is Cocoa, MCL is Carbon ...
      (comp.lang.lisp)
    • Re: Lisp Development on Mac OS X
      ... >> Isn't there also a free edition of LispWorks available for OS X? ... I don't know if they also have Mac ... > all supported platform ... ... which causes MCL to be busy all the time - which is no good idea ...
      (comp.lang.lisp)
    • Re: Compiling Lisp
      ... > apps delivered with LispWorks: ... (The Mac version is written in MCL I think.) ... Andras ...
      (comp.lang.lisp)