Folks:
I am getting a build failure when I:
#' @importFrom utils shortPathName
which roxygenizes it to the NAMESPACE.
I suspect this is because this particular function is Windows-only, but I'm
a bit confused how I should "properly" importFrom a function like this so
it doesn't cause a build fai
I'm a little confused when documenting my code using Imports vs. Depends.
If I have an example in my .Rd that uses a library that is listed under
Imports, it doesn't work, but if it is listed under Depends, it does. What
is the proper way to go about using examples that rely on an Imports?
Should
R-developers:
I'm beginning to work on a manuscript for a set of functions I
developed for a package I have on CRAN (spatial.tools), and I'd like
to rename a function in my package to give a better idea of what it
does prior to manuscript submission -- is there a "safe" way to do a
backwards-compa
R-developers:
I'm working on updating my R package "spatial.tools", and one thing I
was wondering was the proper way to have hidden functions -- should I
simply not export them to the namespace and use the ::: operator to
call them (which is what I currently do)?
--j
--
Jonathan A. Greenberg, Ph
documentation (since they are only used internally by a
larger, documented function -- no end-user would touch them). If this
is flawed understanding, do I just export it to the NAMESPACE and I'm
good to go?
--j
On Fri, Jul 12, 2013 at 11:35 AM, Duncan Murdoch
wrote:
> On 13-07-12 5:52 PM,
I had a similar question awhile ago. Basically, my understanding is
if it is a function, it needs to be documented UNLESS you are calling
it via :::
--j
On Thu, Aug 29, 2013 at 1:11 PM, Sana Wajid wrote:
> Thank you all, I appreciate your responses. Just a quick follow up
> question: couple of
ng it from another package (and see
> the lengthly recent discussion on that issue). The key distinction is
> whether the function is exported or not: You must document any
> function that you export. You don't have to document any function you
> don't export.
>
> Hadley
R-developers:
I had a quick question for the group -- let's say a package I am
developing depends on a single, small function from a large
CRAN-listed package. I can, of course, set a dependency within my own
package, but are there means by which I can include the R script + man
file DIRECTLY in
R-developers:
Duncan Murdoch suggested I move a post I started on r-help over here,
since it is more at the developer level. Here is my
question/challenge -- to my knowledge, there is not currently an
official way to store a *package*'s options to a standardized location
on a user's computer. Gi
I'm working on an update for my CRAN package "spatial.tools" and I noticed
a new warning when running R CMD CHECK --as-cran:
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Jonathan Asher Greenberg '
Depends: includes the non-default packages:
'sp' 'raster' 'rgdal' 'mmap' 'abind' 'par
:
> On 13-10-20 4:43 PM, Jonathan Greenberg wrote:
>
>> I'm working on an update for my CRAN package "spatial.tools" and I noticed
>> a new warning when running R CMD CHECK --as-cran:
>>
>> * checking CRAN incoming feasibility ... NOTE
>> Maintai
One more follow-up -- will I now need to include a library() statement in
each function?
--j
On Sun, Oct 20, 2013 at 3:58 PM, Gabor Grothendieck wrote:
> On Sun, Oct 20, 2013 at 4:49 PM, Duncan Murdoch
> wrote:
> > On 13-10-20 4:43 PM, Jonathan Greenberg wrote:
> >>
&
> On 20 October 2013 at 16:20, Jonathan Greenberg wrote:
> | One more follow-up -- will I now need to include a library() statement in
> | each function?
>
> No.
>
> NAMESPACE entry, coupled with Imports: in DESCRIPTION.
>
> Dirk
>
> --
> Dirk Eddelbuettel | e.
R-developers:
I have a small python script that I'd like to include in an R package I'm
developing, but I'm a bit unclear about which subfolder it should go in. R
will be calling the script via a system() call. Thanks!
--j
--
Jonathan A. Greenberg, PhD
Assistant Professor
Global Environmental
about specifying which should be used?
>>>
>>
>> You ask the user to tell you the path or at least the command name, e.g.
>> by an environment variable or R function argument. Just like any other
>> external program such as GhostScript.
>>
>
> Yes, but s
15 matches
Mail list logo
