Re: [Rd] Problem during "make" with the devel version R-2.3.0 under Sun OS

Thank you very much for your help, and sorry for any inconvevience. Your are rigth my current compiler version is too old : 3.3.2. I will upgrade it immediately. All the best and thanks again Simon Prof Brian Ripley wrote: > This is a compiler error (generating invalid assembler), not an R

Re: [Rd] Utilizing the internet module

On Thu, 23 Feb 2006, Prof Brian Ripley wrote: > On Thu, 23 Feb 2006, Jeffrey Horner wrote: > >> Hello all, >> >> I'd like to utilize the R_Sock* functions from R_ext/R-ftp-http.h in my >> R package. The intent is to use these in conjunction with R_serialize() >> to store R objects in a remote dat

[Rd] Minor Typo in image.Rd

Currently: == \arguments{ [...] \item{xlab, ylab}{ [...] Default to the \sQuote{call names} of \code{x} or \code{y}, or to \code{""} if these where unspecified.} ^ Should read: ==

Re: [Rd] Links to non-vignette documentation

On 2/23/2006 10:02 PM, hadley wickham wrote: >> They are meant to replace the INDEX, which you shouldn't need to create >> any more. The DESCRIPTION file is still needed, but it contains more >> structured information meant for mechanical reading and processing; the >> package man page is meant to

Re: [Rd] Minor Typo in image.Rd

Thanks, I'll fix this. Duncan Murdoch On 2/24/2006 4:12 AM, Paul Roebuck wrote: > > > > Currently: > == > \arguments{ > [...] > \item{xlab, ylab}{ > [...] > Default to the \sQuote{call names} of \code{x} or \code{y}

Re: [Rd] Links to non-vignette documentation

Le 24.02.2006 01:26, Berwin A Turlach a écrit : > G'day all, > > seems as if I must have slept through most of this most interesting > discussion. :) > > >> "BR" == Prof Brian Ripley <[EMAIL PROTECTED]> writes: >> > > BR> On Thu, 23 Feb 2006, hadley wickham wrote: >

Re: [Rd] Links to non-vignette documentation

On 2/24/2006 7:27 AM, Romain Francois wrote: > > What about using the latex package pdfpages to copy the pages from your > PDF file `interface96.pdf` to your Sweave file. (I don't know if it is > compatible with Sweave). > > Not tested : > > \documentclass[a4paper]{article} > %\VignetteIndexEn

Re: [Rd] Links to non-vignette documentation

> No, there's no automatic building after the promptPackage call. It's up > to you to decide which functions need to be mentioned to users. In > large packages it usually doesn't make sense to list all the functions, > so the package writer needs to use judgement here. There are other > mechanis

Re: [Rd] Links to non-vignette documentation

Duncan Murdoch wrote: >>\usepackage{pdfpages} > That's a nice hack. You probably want the "fitpaper" option on the > \includepdf command, so that you don't get an extra border around the > page. For example, this file test.Rnw > The only disadvantages I see are that both the test.pdf and res

Re: [Rd] Utilizing the internet module

Prof Brian Ripley wrote: > On Thu, 23 Feb 2006, Jeffrey Horner wrote: [...] >> On a related note, how do I serialize() an R object to a database >> table column of type BLOB? I've tried using RODBC but was >> unsuccessfully (see R-sig-DB in Feb archive). I've also looked into >> RMySQL/DBI but I

Re: [Rd] Links to non-vignette documentation

On 2/24/2006 9:29 AM, hadley wickham wrote: >> No, there's no automatic building after the promptPackage call. It's up >> to you to decide which functions need to be mentioned to users. In >> large packages it usually doesn't make sense to list all the functions, >> so the package writer needs to

Re: [Rd] Links to non-vignette documentation

On 2/24/2006 11:42 AM, hadley wickham wrote: >> > When was this form of package documentation created? How are users >> > supposed to know it exists? I couldn't find any pointers to it from >> > ?help, ?library or from help(package=XXX). >> >> It's described in the Writing R Extensions Manual, in

[Rd] Rcpp, best method for linking to

Dear all, After a bit of reading I came across the Rcpp example package. There are a few classes that I would like to use and I am not sure how best to include them in my own package. Is it best to compile it as an independent library and link to it? Or is there some way to `require` it for m

Re: [Rd] Rcpp, best method for linking to

Hi Andy, Follow the suggestions for c++ in the Writing R Extensions document. Wrap your c++ code in extern "C"{}, include your classes in the includes (e.g., #include "myclass.h") and put the myclass.h and myclass.cpp in the src directory along with your other code. Then R CMD build ... and R CMD I

Re: [Rd] Rcpp, best method for linking to

Hi Andy (and Andy), I'm not sure why there should be any licensing issues. R itself is GPL-ed, so I just followed this convention. Of course, you can do it yourself with extern "C" and all that. The purpose of Rcpp.{cpp,hpp} is to enable you to write readable code (for a C++ programmer) while hi

Re: [Rd] Rcpp, best method for linking to

Dominick, Sorry, that's not quite what I was asking. I was asking more of a "best practice" kind of question. My own C++ codes compile fine and are accessible to R with some great #define magic. I was noting that the Rcpp package has some generic classes to handle conversion of SEXP structures t

Re: [Rd] Rcpp, best method for linking to

Andy, Any of the options you mentioned (libRcpp.a, source, etc.) sound fine to me. If the GPL is a problem I am happy to change this to some other open source license (I'm not entirely comfortable with GPL, and used it because R uses it). I'm open to suggestions. Dominick Andrew Garbutt wrote: >

Re: [Rd] Rcpp, best method for linking to

Andrew, On 24 February 2006 at 15:00, Andrew Garbutt wrote: | Sorry, that's not quite what I was asking. I was asking more of a "best | practice" kind of question. My own C++ codes compile fine and are | accessible to R with some great #define magic. I was noting that the | Rcpp package has so

Re: [Rd] Links to non-vignette documentation

G'day all, > "DM" == Duncan Murdoch <[EMAIL PROTECTED]> writes: DM> On 2/24/2006 7:27 AM, Romain Francois wrote: >> >> What about using the latex package pdfpages to copy the pages from your >> PDF file `interface96.pdf` to your Sweave file. Merci beaucoup, I wasn't aware t