Re: [Rd] creating a package in R

2012-04-29 Thread steven mosher
If you want simple step by step instructions for Windows, try this http://stevemosher.wordpress.com/ten-steps-to-building-an-r-package-under-windows/ On Sun, Apr 29, 2012 at 7:08 AM, nossa wrote: > Please give me the necessary links that permits me to create my own > package > inR > > -- > Vi

Re: [Rd] creating a package in R

2012-04-29 Thread Joris Meys
http://lmgtfy.com/?q=writing+an+R+package There you go. On Sun, Apr 29, 2012 at 4:28 PM, R. Michael Weylandt < michael.weyla...@gmail.com> wrote: > http://cran.r-project.org/doc/manuals/R-exts.pdf > > Ships with every distribution of R > > Michael > > On Apr 29, 2012, at 10:08 AM, nossa wrot

Re: [Rd] creating a package in R

2012-04-29 Thread R. Michael Weylandt
http://cran.r-project.org/doc/manuals/R-exts.pdf Ships with every distribution of R Michael On Apr 29, 2012, at 10:08 AM, nossa wrote: > Please give me the necessary links that permits me to create my own package > inR > > -- > View this message in context: > http://r.789695.n4.nabble.com/c

[Rd] creating a package in R

2012-04-29 Thread nossa
Please give me the necessary links that permits me to create my own package inR -- View this message in context: http://r.789695.n4.nabble.com/creating-a-package-in-R-tp4596411p4596411.html Sent from the R devel mailing list archive at Nabble.com. __

Re: [Rd] A doubt about substitute() after delayedAssign()

2012-04-29 Thread Duncan Murdoch
On 12-04-29 3:30 AM, Philippe Grosjean wrote: > Hello, > > ?delayedAssign presents substitute() as a way to look at the expression > in the promise. However, > > msg<- "old" > delayedAssign("x", msg) > msg<- "new!" > x #- new! > substitute(x) #- x (was 'msg' ?) > > Here, we just got 'x'... shouldn

[Rd] A doubt about substitute() after delayedAssign()

2012-04-29 Thread Philippe Grosjean
Hello, ?delayedAssign presents substitute() as a way to look at the expression in the promise. However, msg <- "old" delayedAssign("x", msg) msg <- "new!" x #- new! substitute(x) #- x (was 'msg' ?) Here, we just got 'x'... shouldn't we got 'msg'? Same result when the promise is not evaluated