search for: commonlisps

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

Did you mean: commonlisp
2003 Sep 06
2
[LLVMdev] languages, semantic trees, LLVM interfaces
Hello Vikram, Saturday, September 6, 2003, 9:10:45 PM, you wrote: VSA> For any language with relatively sophisticated syntax and semantic VSA> rules, you will probably need a higher-level representation like an VSA> Abstract Syntax Tree in order to do type-checking and other kinds of VSA> checking. OK, concerning AST -- I see. Thank you. VSA> For OCAML, for example, the
2006 Jan 17
0
xlispstat and R
...em, it still works, it's got some reasonable (though old) tools, numerically it needs a good bit of work and updating, but for a 17-year old program, it works quite nicely. Dynamic graphics are comparable to GGobi's (more flexible, but less scalable). Plus, it truly works cross platform. CommonLispStat is fast (SBCL and CMUCL are compiled, not interpreted, commonlisps), but needs a bit of work with numerics (SBCL isn't stable), and Graphics (CLISP doesn't quite like it yet; though tk and gtk2 supported), and decisions about object systems (the old prototypes vs. CLOS) are still open,...
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
> VSA> For OCAML, for example, the front-end 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
2005 Jan 30
2
Patch : fix configure.in and Makefile.am problems.
On Sun, 30 Jan 2005 10:45:05 -0800 (PST) Josh Coalson <xflac@yahoo.com> wrote: > OK, thanks, checked in. once linux-ppc is ironed out the > release should be ready to go. Long way to go yet. Mine is a G3 PowerPC so it doesn't have Altivec. I've tried --disable-assembler but there's still something screwed up int the Makefile.am. Erik --
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