search for: commonlisp

Displaying 8 results from an estimated 8 matches for "commonlisp".

2003 Sep 06
2
[LLVMdev] languages, semantic trees, LLVM interfaces
...is quite sophisticated VSA> and complex and the LLVM representation would not be suitable for VSA> supporting all the checking and translation. But I have just meant ocamlyacc, i.e. ocaml clone of the yacc. And here my question was: what kind of interface is expected to use from within ocml, CommonLisp implementations, Haskel and other nice language implementations? What is the expected way of interfacing LLVM for those non-C language implementations? shared libraries with plain C-interface or what? Kind regards, -- Valery A.Khamenya mailto:khamenya at mail.ru Local Time: 2...
2006 Jan 17
0
xlispstat and R
...> Just curious how xlispstat is used in the industry and what's it strengthen > compared with other computing languages such as R or matlab? Almost not at all, though there are a few holdouts. On a related note, I've been doing some interesting things with a branch of LispStat for CommonLisp. It'll be more interesting when R gets embedded (now it's back on topic). Rumor has it that R is embedded within SBCL, which makes for an interesting distributed computing environment. It's a nice system, it still works, it's got some reasonable (though old) tools, numerically it...
2008 Jul 09
1
lib64
> On x86_64, you can either install a 32 or a 64 bit base system. > > If you install a 32 bit base system, then 64 bit libs should be > installed in /lib64, /usr/lib64 and so on. > However, if you install a 64 bit base system, then the 32 bit > libraries should be install in /lib32, /usr/lib32 and so on. That makes more sense, I suppose, is this to allow code that's broken
2003 Sep 09
0
[LLVMdev] languages, semantic trees, LLVM interfaces
...A> and complex and the LLVM representation would not be suitable for > VSA> supporting all the checking and translation. > > But I have just meant ocamlyacc, i.e. ocaml clone of the yacc. > And here my question was: what kind of interface is expected to use > from within ocml, CommonLisp implementations, Haskel and other nice > language implementations? What is the expected way of interfacing > LLVM for those non-C language implementations? shared libraries with > plain C-interface or what? Valery, This is a good question and I don't think we have a good answer yet....
2005 Jan 30
2
Patch : fix configure.in and Makefile.am problems.
...------------------------------+ Erik de Castro Lopo nospam@mega-nerd.com (Yes it's valid) +-----------------------------------------------------------+ "Any sufficiently complicated C or Fortran program contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of CommonLisp." -- Greenspuns Tenth Rule Of Programming
2003 Sep 06
2
[LLVMdev] languages, semantic trees, LLVM interfaces
Hello LLVM fathers, 1. "languages, semantic trees" what do you think ideally, do languages implementations based on LLVM need internal semantic tree or they should rather try to use LLVM directly in/after syntax parsing? For languages like C++ the expected answer is "of course we need an internal semantic tree between parsing and LLVM!" But I am still
2005 Jan 29
2
Patch : fix configure.in and Makefile.am problems.
Note : I'm subscribed to the list. Please don't CC replies to me. Hi all, I am trying to compiler current CV head on a PowerPC G3 Debain system. Debian test has automake 1.9 which is a little more stringent about errors than 1.8. The following patch has the following fixes. 0) Remove AC_CANNONIAL_HOST because it has already been invoked earlier 1) Make sure
2007 Sep 12
19
Mongrel hangs, consumes all CPU on shutdown
Hi, I''m doing development with Mongrel 1.0.1 on Ruby 1.8.4 / OS X 10.4.10, and I''ve found that often when I shut down my server with ^C, it hangs for a while, gobbling up all CPU. Sometimes it stops after a few seconds, sometimes it''s run for several minutes at least. This happens across all the apps I develop on, but it seems to hang longer after