On Fri, Jul 9, 2010 at 1:27 PM, fendres <[email protected]> wrote: > Hi Leslie, thanks for your clarifications. > > On Jul 8, 1:32 pm, "Leslie P. Polzer" <[email protected]> > wrote: >> fendres wrote: >> > If I eval something >> > within an emacs buffer by M-C-x, where does that happen? >> >> I'm not an Emacs user, but I think it evaluates as Emacs >> Lisp within Emacs, not as Common Lisp within the remote >> SBCL. > > I'm not sure about this, but the key combination is defined > by slime (I found it on http://www.cliki.net/SLIME%20Features), > so I don't think it is emacs' lisp. > >> It's complicated. Are you intent on using Slime for your Common >> Lisp coding? Taking out Slime and using a decoupled editor >> helps simplify things in the beginning. > > On the one hand it simplifies the process, but on the other hand > it is also helpful. Working in the sbcl repl is painful. And the repl > is supposed to be a key feature of lisp development, right? > >> >> > I managed to to connect to my mysql database by executing >> > the clsql-tutorial.lisp file (from clsql/examples) with (load >> > #p"..."). >> > However I during file evaluation I get an error after the connection >> > is established: >> > The value 0 >> > is not of type >> > (OR (VECTOR CHARACTER) (VECTOR NIL) BASE-STRING SYMBOL >> > CHARACTER). >> > [Condition of type TYPE-ERROR] >> >> What's your SBCL version? What's your CLSQL version? > > I installed SBCL via aptitude. The version is: 1.0.29.11.debian. > I don't know where to geht the CLSQL version number from. I > installed it two weeks ago via clbuild, so it should be pretty recent. > The changelog file says, the last change was 2008 though. > > Does this work for everybody else, or is this a general problem I > have? > > I really wanted to get working on a new project and give lisp web > development a try, because I thought it would be an easy entry > (as compared to GUI development) and many people consider it > superior to php/perl/python. > So far it seems really hard to dive in. My usual ways of learning an > API and looking at given code, figuring out such problems don't work. > Googling errors doesn't work that well either, as the community is > tiny, and there is no way of getting a software bundle that you know > is in a coherent state. > I just hope that - with some help - I can put all the initial > problems > behind me. > > Regards, > Felix > > -- > You received this message because you are subscribed to the Google Groups > "weblocks" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/weblocks?hl=en. > >
This community though small, is very productive. SBCL itself is evolving at a fast pace. You have to keep up with it... use clbuild, use it to fetch and compile the latest sbcl, libraries etc. Most often, as with Weblocks, you need the -dev or equivalent bleeding edge as problems you are finding have been fixed and committed. http://weblocks.viridian-project.de/installation Make sure you edit the wnpp-projects file to keep up with the latest - here is ours (The link will automatically keep up with our changes): http://image.rayservers.com/wnpp-projects Also, Leslie is a vim guru. That is an unusual combination in the Lisp world, most of us are on emacs + slime. Lisp has always been for the "keyboard artists" as I call them. The original Lisp machines were amazing man-machine interfaces. In my view once you are familiar with the quick instant compiles of just one function on slime, its hard to go back to anything else. Being able to change a single function in a running web server without a restart is unheard of in other environments still. Also, the lisp process itself is long lived, you can serve everything from RAM. In-memory object searching is way faster than anything tied to disk. You just have to be clever about persisting important data - this is something we are working on. Cheers, ---Venkat. -- http://www.rayservers.com/ -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
