Re: [Rd] tag \href not recognised in rd doc
Back from the field, I have been capable to update to R 2.13.0 today.
\href is well recognised with this version and package check run OK.
Best,
Patrick
Le 06/06/2011 10:59, Duncan Murdoch a écrit :
On 11-06-06 12:41 AM, Patrick Giraudoux wrote:
Le 05/06/2011 22:30, Duncan Murdoch a écrit :
I don't get any error when I insert that code into a .Rd file in R
2.13.0 patched. The NEWS file says this was fixed in 2.12.2 patched.
What version are you using?
Duncan Murdoch
Currently R version 2.12.2 (2011-02-25) binary
Suppose I should move to the 2.13.0 ?
Yes, please do.
Duncan Murdoch
Patrick
On 11-06-05 10:56 AM, Patrick Giraudoux wrote:
Hi,
I have a trouble trying to use \href in a rd doc. See example below:
\references{
\href{http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2702787/}{Vaniscotte
A., Pleydell D., Raoul F., Quere J.P., Coeurdassier M., Delattre
P., Li
T., Qian W., Takahashi K., Weidmann J.C., Qiu J., Giraudoux P. 2009
Modelling and spatial discrimination of small mammal assemblages: an
example from western Sichuan (China). Ecological Modelling, 220:
1218-1231.}
}
The Rcmd check gives:
* checking R code for possible problems ... OK
* checking Rd files ... WARNING
checkRd: (7) multignome.Rd:38: Tag \href not recognized
I saw there is already a link on the issue
http://bugs.r-project.org/bugzilla3/show_bug.cgi?id=14535, but I
hardly
understand if it is a real bug, if so if it have been fixed, or if
I am
misusing the tag...
Any hint appreciated,
Best,
Patrick
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] Detecting development environment
Hi all, Is there a straight-forward, cross-platform way of determining if a user has all the tools needed to develop R packages (i.e. gcc etc)? It doesn't need to be 100%, but should give a rough idea. One idea I had was simply to see if system(R CMD install --help) worked. Hadley -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://had.co.nz/ __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Detecting development environment
From: had...@rice.edu Date: Mon, 13 Jun 2011 09:21:07 -0500 To: r-devel@r-project.org Subject: [Rd] Detecting development environment Hi all, Is there a straight-forward, cross-platform way of determining if a user has all the tools needed to develop R packages (i.e. gcc etc)? It doesn't need to be 100%, but should give a rough idea. One idea I had was simply to see if system(R CMD install --help) worked. You could copy a configure script from just about anywhere and adapt it. Not sure what you would do on 'dohs but the script should be able to support cygwin pretty easily. Hadley -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://had.co.nz/ __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Detecting development environment
On Jun 13, 2011, at 10:21 AM, Hadley Wickham wrote:
Hi all,
Is there a straight-forward, cross-platform way of determining if a
user has all the tools needed to develop R packages (i.e. gcc etc)?
It doesn't need to be 100%, but should give a rough idea. One idea I
had was simply to see if system(R CMD install --help) worked.
That's not really checking pretty much anything (even if you used INSTALL ;))
since all it does is to run R.
More reasonable quick check may be R CMD SHLIB, though, since that involves
both make and gcc:
echo 'void foo(int *bar) { *bar=1; }' foo.c R CMD SHLIB foo.c
And you could even check feasibility with something like
dyn.load(paste(foo,.Platform$dynlib.ext,sep=''))
stopifnot(.C(foo,0L)[[1]] == 1L)
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Detecting development environment
One option would be to use autoconf and automake, and related tools. That is exactly what they're designed for, in the simplest case. In more advanced cases, I have seen them used to verify not only the existance of selected tools and libraries, but also whether or not the implementation of selected functions is buggy (as you may be aware, some implementations of the standard C library leave a bit to be desired, at least for some functions). But you do have a little work to do to write some of the input files they need; and you can make them flexible in terms of supporting telling them were certain resources are located. That said, the documentation for them is pretty good relative to the norm for unix like platforms. As for being cross platform, I know they're available (or can be built) for unix like platforms, and on Windows via cygwin (which I suppose counts as unix-like). I don't know about other platforms, and I don't know if you can get them to work on Windows without cygwin (maybe as an addition to RTools?). As for being straight-forward, I had directed a student to begin studying autoconf/automake upon finishing a study of Gnu make, and the first day he did so, he met with success and asked me, was it supposed to be this straightforward? This, from a guy that has only begun studying programming! BTW: he told me he planned to study R once he had mastered C++ and QuantLib. He has a strong interest in quantitative finance, and so would be looking at those R packages related to quantitative finance. I suppose whether or not it is 100% depends on the quality of inputs you provide. HTH Ted -Original Message- From: r-devel-boun...@r-project.org [mailto:r-devel-bounces@r- project.org] On Behalf Of Hadley Wickham Sent: June-13-11 10:21 AM To: r-devel@r-project.org Subject: [Rd] Detecting development environment Hi all, Is there a straight-forward, cross-platform way of determining if a user has all the tools needed to develop R packages (i.e. gcc etc)? It doesn't need to be 100%, but should give a rough idea. One idea I had was simply to see if system(R CMD install --help) worked. Hadley -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://had.co.nz/ __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] Participation Requested: Survey about Open-Source Software Development
Hi, Drs. Jeffrey Carver, Rosanna Guadagno, Debra McCallum, and Mr. Amiangshu Bosu, University of Alabama, and Dr. Lorin Hochstein, University of Southern California, are conducting a survey of open-source software developers. This survey seeks to understand how developers on distributed, virtual teams, like open-source projects, interact with each other to accomplish their tasks. You must be at least 19 years of age to complete the survey. The survey should take approximately 15 minutes to complete. If you are actively participating as a developer, please consider completing our survey. Here is the link to the survey: http://goo.gl/HQnux We apologize for inconvenience and if you receive multiple copies of this email. This survey has been approved by The University of Alabama IRB board. Thanks, Dr. Jeffrey Carver Assistant Professor University of Alabama (v) 205-348-9829 (f) 205-348-0219 http://www.cs.ua.edu/~carver __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Detecting development environment
Is there a straight-forward, cross-platform way of determining if a
user has all the tools needed to develop R packages (i.e. gcc etc)?
It doesn't need to be 100%, but should give a rough idea. One idea I
had was simply to see if system(R CMD install --help) worked.
That's not really checking pretty much anything (even if you used INSTALL ;))
since all it does is to run R.
Well I guess it checks that you have your path set up right. But this
is why I asked ;)
More reasonable quick check may be R CMD SHLIB, though, since that involves
both make and gcc:
echo 'void foo(int *bar) { *bar=1; }' foo.c R CMD SHLIB foo.c
And you could even check feasibility with something like
dyn.load(paste(foo,.Platform$dynlib.ext,sep=''))
stopifnot(.C(foo,0L)[[1]] == 1L)
Perfect - thanks!
Hadley
--
Assistant Professor / Dobelman Family Junior Chair
Department of Statistics / Rice University
http://had.co.nz/
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
