Re: [Rd] Problem with rnorm ?

2007-05-12 Thread Prof Brian Ripley
1) You are linking an executable against -lR. You can't do that as here, for R is never initialized (and I very much doubt you will be able to give a reference that recommended you to do that). You need to link against standalone libRmath, or start up R properly if you really need R. 2) The

[Rd] Implicit vs explicit printing and the call stack

2007-05-12 Thread hadley wickham
Hi everyone, I've run into a bit of strange problem with implicit vs explicit printing and the call stack. I've included an example at the bottom of this email. The basic problem is that I have an S3 object with a print method. When the object is implicitly printed (ie. typed directly into the

Re: [Rd] Implicit vs explicit printing and the call stack

2007-05-12 Thread Gabor Grothendieck
I can't reproduce that with ggplot 0.4-0 as some of the functions you are using do not appear to be part of ggplot (I suspect you are using a newer version of ggplot than you have released) but the following illustrates the difference using R version 2.5.0 Patched (2007-05-01 r41405) and lattice

[Rd] The best way to use R's linear algebra functions from C

2007-05-12 Thread Daniel Oberski
First of all, thanks to everybody for R. I have written a program in C that requires some basic matrix operations, namely the following: - matrix multiplication and addition, - determinant and transpose, - inverse of a symmetric matrix. Since I am a happy R user I thought I could call R from

Re: [Rd] Problem with rnorm ?

2007-05-12 Thread Tong Wang
It's working , Thanks a lot !!! tong - Original Message - From: Prof Brian Ripley [EMAIL PROTECTED] Date: Saturday, May 12, 2007 4:27 am Subject: Re: [Rd] Problem with rnorm ? To: Tong Wang [EMAIL PROTECTED] Cc: R-devel r-devel@r-project.org 1) You are linking an executable against

[Rd] Strange behavior of debugger

2007-05-12 Thread Tong Wang
Hi, All: I had some trouble debugging C source dynamically loaded into R , when I issued N in gdb(or insight) , the debugger, instead of moving downward step by step, jumped to strange positions (upward, downward, one step, a few steps away). To enter the debugger, I issued