> Marco atzeri writes:
> Hi,
> looking on the build scripts, I noticed on configure.ac
> ##
> ## Completely disable using libtool for building shlibs until libtool
> ## fully supports Fortran and C++.
> ## AC_ARG_WITH([libtool],
> ## [AS_HELP_STRING([--with-libtool],[use libtool for building
On Thu, 8 Sep 2011, Steve Lianoglou wrote:
Hi Simon,
Thanks for the quick response.
Comments in line:
On Thu, Sep 8, 2011 at 4:11 PM, Simon Urbanek
wrote:
On Sep 8, 2011, at 3:59 PM, Steve Lianoglou wrote:
Hi,
Essentially: subject line says it all.
I've created a package that wraps an
Steve,
On Sep 9, 2011, at 8:36 AM, Prof Brian Ripley wrote:
> On Thu, 8 Sep 2011, Steve Lianoglou wrote:
>
>> Hi Simon,
>>
>> Thanks for the quick response.
>>
>> Comments in line:
>>
>> On Thu, Sep 8, 2011 at 4:11 PM, Simon Urbanek
>> wrote:
>>>
>>> On Sep 8, 2011, at 3:59 PM, Steve Lianog
Hi Simon, Prof. Ripley, and Dirk,
First: thanks again for the tips, it's great to have some of the "top
bRass" providing this type of help.
Last (few) comments in line:
On Fri, Sep 9, 2011 at 9:41 AM, Simon Urbanek
wrote:
> On Sep 9, 2011, at 8:36 AM, Prof Brian Ripley wrote:
>> On Thu, 8 Sep 2
Hi,
I'm asking another one of those questions that would be obvious if I
could watch your work while you do it.
I'm having trouble understanding the workflow of code and package maintenance.
Stage 1. Make some R functions in a folder. This is in a Subversion repo
R/trunk/myproject
Stage 2. M
On Fri, Sep 9, 2011 at 11:38 AM, Paul Johnson wrote:
> Hi,
>
> I'm asking another one of those questions that would be obvious if I
> could watch your work while you do it.
>
> I'm having trouble understanding the workflow of code and package maintenance.
>
> Stage 1. Make some R functions in a f
I write the *.Rd file including examples that I use as unit tests
before I write the code. Others criticize this approach insisting that
\examples is NOT a place for unit tests. There are unit testing
protocols for R that I have not learned. Instead, I rely on \dontshow
inside \example
On 9 September 2011 at 11:38, Paul Johnson wrote:
| Hi,
|
| I'm asking another one of those questions that would be obvious if I
| could watch your work while you do it.
|
| I'm having trouble understanding the workflow of code and package maintenance.
|
| Stage 1. Make some R functions in a f
On 09/09/2011 12:38 PM, Paul Johnson wrote:
Hi,
I'm asking another one of those questions that would be obvious if I
could watch your work while you do it.
I'm having trouble understanding the workflow of code and package maintenance.
Stage 1. Make some R functions in a folder. This is in a
On 9/9/2011 10:47 AM, Duncan Murdoch wrote:
On 09/09/2011 12:38 PM, Paul Johnson wrote:
Hi,
I'm asking another one of those questions that would be obvious if I
could watch your work while you do it.
I'm having trouble understanding the workflow of code and package
maintenance.
Stage 1. Ma
I am running into the following issue that has been previously
reported on the R-devel mailing list. The short version is that I'm
writing a package for MPI, and I'd like to change CC and SHLIB_LD to
"mpicc". Trying to change them in Makevars.in has no effect, because
the values are clobbered by /e
>> If you write the *.Rd file before (like Spencer) or soon after writing the
>> code, then design errors will usually stick out at you, and you can modify
>> the functions. If you keep your functions small, you'll get them working
>> early, and won't have a lot of problems keeping them in sync wi
> | In other languages, I've seen to write the documentation inside the
> | code files and then post-process to make the documentation. Is there
> | a similar thing for R, to unify the R code development and
> | documentation/package-making process?
>
> You can also follow the cool kids who these
Hello,
I have recently been doing some research regarding how to successfully save
and load Rcpp Objects ( objects from modules ) for future use, but with
little success. For example, to use the example package (from package
skeleton) in Rcpp:
>library(Rcpp)
>Rcpp.package.skeleton("rdevelhelp", m
On Sep 9, 2011, at 10:30 AM, Steve Lianoglou wrote:
> Hi Simon, Prof. Ripley, and Dirk,
>
> First: thanks again for the tips, it's great to have some of the "top
> bRass" providing this type of help.
>
> Last (few) comments in line:
>
> On Fri, Sep 9, 2011 at 9:41 AM, Simon Urbanek
> wrote:
>
Hi Simon,
On Fri, Sep 9, 2011 at 5:32 PM, Simon Urbanek
wrote:
>
> On Sep 9, 2011, at 10:30 AM, Steve Lianoglou wrote:
>
>> Hi Simon, Prof. Ripley, and Dirk,
>>
>> First: thanks again for the tips, it's great to have some of the "top
>> bRass" providing this type of help.
>>
>> Last (few) comment
Hola,
On 9 September 2011 at 16:07, Michael King wrote:
| Hello,
|
| I have recently been doing some research regarding how to successfully save
| and load Rcpp Objects ( objects from modules ) for future use, but with
| little success. For example, to use the example package (from package
| ske
+1 for roxygen2, lazycoolness oblige.
An alternative that has not been mentioned is inlinedocs,
http://inlinedocs.r-forge.r-project.org/
I don't use it myself, but it might appeal to your workflow.
baptiste
On 10 September 2011 06:41, Hadley Wickham wrote:
>> | In other languages, I've seen to
18 matches
Mail list logo
