similar to: xlispstat and R

Well, nothing has changed in the issues that I brought up earlier, except that I can confirm core dumps in non-threaded lisps as well (CLISP), using svn version 37840 (this morning, Seattle time) for R-2-3-patches. I've not tried Thomas' suggested fixes, as I'm hesistant to go down the road of fixing R in such a way that would require constant patching. (so for those counting,

With regard to Bartlett-style collectors, they are also used in CMUCL/SBCL, OpenDylan, and various products based on Ravenbrook's Memory Pool System. Also, while Mono doesn't use a Bartlett-style collector, it does support pinning objects referenced from ambiguous stack roots, in an otherwise copying collector. While ITA has expressed concerns with SBCL's GC, they seem to involve the

I am sorry for this off-topic question. Just curious how xlispstat is used in the industry and what's it strengthen compared with other computing languages such as R or matlab? Thanks a lot. [[alternative HTML version deleted]]

I came across a quite interesting post from Ross Ihaka, thought would be good to share it and get the opinion of folks around here. I am not sure where to post this for the R community but since it has to do with development I thought or R-devel Ross Ihaka Newsgroups: comp.lang.lisp From: Ross Ihaka <ih... at stat.auckland.ac.nz> Date: Wed, 23 Jan 2008 10:35:26 +1300 Local: Tues, Jan 22

Dear R users, I was trying to install the package RXLisp by Duncan Temple Lang on a MDK 9.1 Linux machine running R 1.8.0 installed from a RPM. Unfortunately I had a problem loading the shared library into R. Since I'm a Linux newbie I was not able to solve the problem. Maybe some of you can help me. First of all I downloaded the source archive for Xlisp-Stat and for the RXlisp package.

I have been taking a break for the last month or so, and am only just now catching up on my email. Otherwise, I would have joined this discussion earlier. And... I apologize for the length of this, but I don't think it is overly long. >From the amount of activity in the LispStat news group (none), it seems that LispStat is dead. We all know that Luke is working on R and not on LispStat,

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

Hi, This is just to report about the "alignment check: 0000 [#1] SMP" kernel messages in one of my build system (domU) running Scientific Linux 6.1. I am compiling/rpm package for sbcl (http://sbcl.sourceforge.net/) in my build system (domU) and hit the following kernel messages although the domU in question still running and compilation still in progress. I have done some searching

On 7/23/19 8:42 PM, John McCall via llvm-dev wrote: > > On 21 Jul 2019, at 12:29, James Y Knight via llvm-dev wrote: > > Yes, indeed! > > The SBCL lisp compiler (not llvm based) used to emit functions > which would > return either via ret to the usual instruction after the call, or > else load > the return-address from the stack, then jump 2

Yes, indeed! The SBCL lisp compiler (not llvm based) used to emit functions which would return either via ret to the usual instruction after the call, or else load the return-address from the stack, then jump 2 bytes later (which would skip over either a nop or a short jmp at original target location). Which one it used depended upon whether the function was doing a multi-valued return (in which

rsync.r-project.org has been updated to serve the sources for R-0.99.0. There are three versions of the R CVS source tree available for anonymous rsync. $ rsync rsync.r-project.org:: r-release R sources (feature-frozen version) CVS tree (approx 12 MB) r-release-patched patched R sources (feature-frozen version) CVS tree (approx 12 MB) r-devel R sources (development version) CVS

rsync.r-project.org now offers three flavors of the R sources. $ rsync rsync.r-project.org:: r-release R sources (feature-frozen version) CVS tree (approx 10 MB) r-release-patched patched R sources (feature-frozen version) CVS tree (approx 10 MB) r-devel R sources (development version) CVS tree (approx 10 MB) xlispstat xlispstat sources (development version) CVS tree

"Hodgess, Erin" <HodgessE at zeus.dt.uh.edu> writes: > Hello all! Good to hear from you again, Erin. > I would like to download R to the UNIX machine here. > > I will be downloading it to my own account. > > Could anyone please tell me how much space it requires once it is > "unzipped"? The original tree is about 8.5 MB. After compilation you

Sources for R-1.7.0 are now available through rsync to rsync.r-project.org. $ rsync rsync.r-project.org:: r-release R-1.7.0 sources (current released version - approx 30 MB) r-patched R sources (patched released version - approx 30 MB) r-devel R sources (development version) r-manuals Development sources for manuals for R r-recommended Sources for recommended R

Sources for R-1.7.0 are now available through rsync to rsync.r-project.org. $ rsync rsync.r-project.org:: r-release R-1.7.0 sources (current released version - approx 30 MB) r-patched R sources (patched released version - approx 30 MB) r-devel R sources (development version) r-manuals Development sources for manuals for R r-recommended Sources for recommended R

Dear ESS users, {BCC'ed to RPM and Debian maintainers of ESS} We have now released ESS 5.2.7. This is a bug fix release against 5.2.6 where - the new UTF-8 "support" gave problems for Xemacs, and - accidentally, 'auto-fill-mode' was activated for *.R buffers with a few new features, see "New Features" below , notably some extended Sweave supported,

Hello. I was wondering how one can find the exact values of the range of an axis within a plot. In xlispstat it was (send plot :range 0). Thanks much, Jason

> 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

thomas weidner wrote: > Hello, > > i want to implement a common lisp subset using llvm for fun. Out of curiousity, for which CL implementation is this targeted? sbcl? Or something you're rolling? The reason why I ask is that I expressed an outrageous opinion at Supercomputing back in November, to wit, that CL is probably the best language suited for today's multicore

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 --