Re: [Rd] R v2.10.0: Doc clarification for cross references and where are we heading?

2009-09-23 Thread Romain Francois
On 09/24/2009 05:21 AM, Gabor Grothendieck wrote: On Wed, Sep 23, 2009 at 10:54 PM, Duncan Murdoch wrote: - Ways to link from man pages to vignettes. The reverse would be nice, but it's not possible with the current design, so that would be far off. If feasible I would like to be able to

Re: [Rd] R v2.10.0: Doc clarification for cross references and where are we heading?

2009-09-23 Thread hadley wickham
> You want the filename to be an alias because links sometimes go to aliases > and sometimes to filenames; you want the name to match because that's what > is displayed at the top of the page, so people might remember "just go to > the Foo man page". It would be really good to emphasise this somew

Re: [Rd] R v2.10.0: Doc clarification for cross references and where are we heading?

2009-09-23 Thread Gabor Grothendieck
On Wed, Sep 23, 2009 at 10:54 PM, Duncan Murdoch wrote: > >  - Ways to link from man pages to vignettes.  The reverse would be nice, but > it's not possible with the current design, so that would be far off. > If feasible I would like to be able to link to any text, html or pdf file in the packag

Re: [Rd] R v2.10.0: Doc clarification for cross references and where are we heading?

2009-09-23 Thread Duncan Murdoch
On 23/09/2009 10:08 PM, Henrik Bengtsson wrote: Hi, in 'Writing R Extensions" of R v2.10.0, under Section 'Cross-references' (2009-09-07) it says: 1. "The markup \link{foo} (usually in the combination \code{\link{foo}}) produces a hyperlink to the help for foo. Here foo is a topic, that is the

[Rd] R v2.10.0: Doc clarification for cross references and where are we heading?

2009-09-23 Thread Henrik Bengtsson
Hi, in 'Writing R Extensions" of R v2.10.0, under Section 'Cross-references' (2009-09-07) it says: 1. "The markup \link{foo} (usually in the combination \code{\link{foo}}) produces a hyperlink to the help for foo. Here foo is a topic, that is the argument of \alias markup in another Rd file (poss

Re: [Rd] Crash due to extreme example

2009-09-23 Thread Duncan Murdoch
On 23/09/2009 7:10 PM, Saptarshi Guha wrote: Hello, I was trying this bit of code (i know it is an extreme case) g=function(r){ if(r==1) return(list(x=1)) else return(list(x=g(r-1))) } For z=g(500), the code runs but when I print z i.e >> z I get *** caught bus e

[Rd] Crash due to extreme example

2009-09-23 Thread Saptarshi Guha
Hello, I was trying this bit of code (i know it is an extreme case) g=function(r){ if(r==1) return(list(x=1)) else return(list(x=g(r-1))) } For z=g(500), the code runs but when I print z i.e >> z I get *** caught bus error *** address 0x1, cause 'non-existent physical

[Rd] FW: RE: Bug 13937 (setRepositories() doesn't allow graceful cancellation from GUI menu) (PR#13969)

2009-09-23 Thread richcalaway
Hi, again- But I see the behavior has been fixed in the current R-devel build, so sorry for the noise, and thanks for keeping R such a great package! --Rich Calaway _ From: Rich Calaway [mailto:richcala...@revolution-computing.com] Sent: Wednesday, Se

Re: [Rd] Bug 13937 (setRepositories() doesn't allow graceful cancellation from GUI menu) (PR#13968)

2009-09-23 Thread richcalaway
Hi, all- This one was moved to features&FAQ, which appears to be the "works as documented" folder, with the following note: intentional: you do need to set repositories or interrupt R. If this is true, there's still a bug, and in fact two of them: the graphical menu dialog should have no Cancel

[Rd] warnings handled oddly in functions with browser calls (PR#13967)

2009-09-23 Thread richcalaway
Full_Name: Rich Calaway Version: 2.9.2 OS: Windows Vista Submission from: (NULL) (65.47.30.18) Consider the following function: myfun <- function(){ print(log(-1)) browser() print("Good-bye!") } In the default case, with options(warn=0), if I call this function and type

Re: [Rd] enabling core dumps

2009-09-23 Thread pleydell
usually what happens is (# meant to be a comment char) % R -d gdb -f test.R gdb> run ...segfault happens, breaks into gdb gdb> bt # print the backtrace gdb> up # move up the stack, to get to 'your' frame gdb> l # show source listing, use -O0 compiler flag, see gdb> help dir gdb> print some

Re: [Rd] Strange behaviour with global variable in C

2009-09-23 Thread pleydell
To answer my own question... I have two copies of my program 1) a working copy stored in $PROJECT/analysis/c 2) a packaged copy stored in $PROJECT/analysis/myPackage_1.0.2.tar.gz I have been running a script which does the following library(myPackage) load(myData) detach("package:myPackge") dy

[Rd] Strange behaviour with global variable in C

2009-09-23 Thread pleydell
I understand global variables can be a bad idea, but even so I would like to understand what is going on here... ### DESCRIPTION OF PROGRAM ### ...I have a strange bug on a global variable in some C code which I am compiling using $ MAKEFLAGS="CFLAGS=-g -O0" R CMD SHLIB myProgram.c the global v

Re: [Rd] A couple of suggestions: source function (package base)

2009-09-23 Thread Jose Claudio Faria
The extra "\n" is located at line 142 of the current source function: cat("\n", dep, if (do.trunc)... HTH, -- ///\\\///\\\///\\\///\\\///\\\///\\\///\\\///\\\ Jose Claudio Faria Estatistica - prof. Titular UESC/DCET/Brasil joseclaudio.fa...@gmail.com ///\\\///\\\///\\\///\\\///\\\///\\\///\\\///

[Rd] R + C + Lapack toy regression example

2009-09-23 Thread Vinh Nguyen
dear list, since matrix manipulations is often of interest in statistical computations, i'd like to get a working example of using Lapack for regression. However, i run into an error. My matrix-lapack-example.c file: #include void reg(const char* trans, const int* m, const int* n, con