Re: Fwd: Intel native MCL

 From yesterday's optimistic post about how much further ahead Clozure 
CL's GUI has moved, I thought I'd try out Clozure CL (Clozure 
CL64.app that I built last September) and run a small and trivial 
function that I wrote over the weekend on MCL. The file was so small 
I just copied the clipboard contents from the PPC to the Intel 
machine and pasted it into a new Clozure CL buffer, saved it, and 
then evaluated it.

It worked fine. It just prints out 5 lines of text with some numbers 
and symbols. Nothing esoteric.

However, it worked only once. Now doing command-E, command-shift-E, 
etc. has no more effect.

Even typing (+ nil 5) into the file editor and trying to evaluate 
this form to get an error (either by selecting it via the mouse or 
through the menus) has no effect. It seems like Hemlock has died.

And I have absolutely no clue what is wrong or what needs to be done 
... except restart the app.

I guess everyone has a different threshold at which they will start 
yelling at the computer and launching MCL.


>There will never be an Intel-native MCL. It's too much work for too 
>little gain.
>
>That's the bad news. The good news is that Clozure CL is of course 
>already Intel-native and its compiler is superior to MCL's in many 
>ways beyond just being Intel-native.
>
>CCL's Cocoa IDE is not yet quite up to the facility of MCL's IDE, 
>but it's getting close. I've been using it exclusively for Lisp 
>development for about 6 months now, and it's good enough that I no 
>longer find myself periodically yelling at the computer and 
>launching MCL. It's moved from alpha quality to beta quality.
>
>One thing that would be very helpful in improving the CCL Cocoa IDE 
>is for MCL veterans to use it and provide feedback (to Clozure or to 
>this list) of your top n "dealbreaker" issues that you need working 
>to make the CCL IDE usable. As I said, my dealbreakers list is now 
>empty and I'm working on my "it would be very nice if" list, but if 
>you have any dealbreakers of your own please voice them.
>
>Clozure and several volunteers are working on the IDE and your 
>feedback always helps them prioritize issues.
>
>Shannon Spires
>
>
>Begin forwarded message:
>
>>From: Benjamin Perrault 
>><<mailto:[email protected]>[email protected]>
>>Date: June 4, 2011 6:00:40 PM MDT
>>To: <<mailto:[email protected]>[email protected]>
>>Subject: [info-mcl] Intel native MCL
>>Reply-To: Discussion list for MCL users 
>><<mailto:[email protected]>[email protected]>
>>
>>I've been using MCL a lot (again) lately, but one looming concern I 
>>have is it seems to still be very much a PPC centric app ( or I'm 
>> building it wrong because it always comes out as one ).
>>
>>Has there been any progress on making it an intel native app, as 
>>Lion appears to have no PPC support?
>>
>>This is something I've just realized and MCL ( and MCLIDE, which I 
>>use for Clojure and Clozure CL ) seem to be the only non-intel apps 
>>I have let and there really is no replacement for either of them....
>>
>>Anyway - just curious if that ball is rolling. I'm not good enough 
>>of a lisp hack to help much on that low of a level but I wanted to 
>>ask...
>>
>>cheers and thanks,
>>-bp
>>_______________________________________________
>>info-mcl mailing list
>><mailto:[email protected]>[email protected]
>><http://clozure.com/mailman/listinfo/info-mcl>http://clozure.com/mailman/listinfo/info-mcl
>>
>
>_______________________________________________
>info-mcl mailing list
>[email protected]
>http://clozure.com/mailman/listinfo/info-mcl

_______________________________________________
info-mcl mailing list
[email protected]
http://clozure.com/mailman/listinfo/info-mcl