Ruby performance woes
in [Lisp]
|
Prev: comp.lang.lisp charter
Next: Casio Collection Men's GOLD LABEL Edifice Watch - Replica Watch Fake
From: Ken Tilton on 22 Apr 2008 22:51 Brian Adkins wrote: > On Apr 22, 3:52 pm, Ken Tilton <kennytil...(a)optonline.net> wrote: > >>Scott Burson wrote: >> >>>Just came across this... >> >>> http://www.regdeveloper.co.uk/2008/04/21/bray_ruby_rails/ >> >>>You'd think there would be some way for Lisp to fill this gap. >> >>http://gitorious.org/projects/hunchncells > > > "Yet another web-framework. This one uses cells and XMLHttpRequest to > create dynamically updating models on the server that update their > state on the client. > > The dynamically updating bit isn't working yet but hopefully we'll > have it working by the time anyone notices this." > > Too late. Not for my killfile. But thanks for noticing!
From: Willem Broekema on 23 Apr 2008 03:10 On Apr 23, 1:11 am, Jason Nielsen <j...(a)cs.sfu.ca> wrote: > Well I stand corrected by the man himself ;-)! Just out of curiosity I'm > assuming you have dropped the reliance on Allegro's version of yacc. Yep, a slightly extended version of cl-yacc can be used in its place. It is included in the source. > What of the environments stuff? There is a fallback mechanism for keeping state, which uses symbol- macrolet. > If there is nothing major stopping porting I'd be happy to help > out with the leg work of adding a few #+sbcl > (sb-pcl:.... etc. to get this working on sbcl and cmucl. There is a dependency on Closer to Mop, in order to abstract way from the different names for the MOP package. Give the porting a try if you have time, that would be appreciated. :) - Willem
From: Marco Antoniotti on 23 Apr 2008 04:04 On Apr 23, 9:10 am, Willem Broekema <metaw...(a)gmail.com> wrote: > On Apr 23, 1:11 am, Jason Nielsen <j...(a)cs.sfu.ca> wrote: > > > Well I stand corrected by the man himself ;-)! Just out of curiosity I'm > > assuming you have dropped the reliance on Allegro's version of yacc. > > Yep, a slightly extended version of cl-yacc can be used in its place. > It is included in the source. What are the extensions and when will it be folded back in CL-YACC main trunk? Cheers -- Marco
From: Christophe on 23 Apr 2008 04:12 On 23 avr, 00:46, Jason Nielsen <j...(a)cs.sfu.ca> wrote: > On Tue, 22 Apr 2008, Duane Rettig wrote: > > > Or perhaps become implementors of those languages themselves: > > >http://common-lisp.net/project/clpython/ > > Too bad it only runs on Allegro as I doubt this project will gain any > traction among the Pythonista relying on a commercial lisp as its "vm". > If a common lisp system was the "jvm" of today I'd be a happy man... an > open source common lisp system of course ;-)! > > Jason I am curious, but if my memory is good, Lisp is build with an interpreter and compiler. And, it's a better way than just a VM. To finish, what is the interest of use an open source Lisp less good compared to Allegro ? CLPython is an interesting project because it works with good Lisp, commercial, of course. (translation_in_real_world "Open Source" > "the summun of economical hypocrisy." :) Best Regards, Christophe
From: Willem Broekema on 23 Apr 2008 04:30
On Apr 23, 10:04 am, Marco Antoniotti <marc...(a)gmail.com> wrote: > What are the extensions and when will it be folded back in CL-YACC > main trunk? Setting precedence level at production level, in addition to at token level. That allows unary plus/minus (x = +3) to have a different precedence level than binary (x = 1 + 2). That change has been mailed to the author, but he remains silent. The same happened with another small fix to make things work on Allegro. As soon as CL-Yacc integrates it, the copy in CLPython will be removed of course. - Willem |