Hello, All:
I'm getting different answers from "lapply(ts(1:2), length)",
depending on what is attached, with nothing obviously masked.
1. Am I correct that the answer to "lapply(ts(1:2),
length)" should be a list of length 2 consisting of "int 1" twice? This
is what I g
Section 1.3.3 of Writing R Extensions says
"The recommended method of building binary packages is to use
R CMD INSTALL --build pkg where pkg is either the name of a source tarball (in
the usual .tar.gz format) or the location of the directory of the package source
to be built. "
(a) vignette
On 21-10-2013, at 03:38, Simon Urbanek wrote:
> On Oct 20, 2013, at 2:00 AM, Berend Hasselman wrote:
>
>>
>> The subversion log for 2013 (http://developer.r-project.org/R_svnlog_2013)
>> on the R developer page hasn't been updated since September 29. I would
>> appreciate the daily updates
On Oct 20, 2013, at 2:00 AM, Berend Hasselman wrote:
>
> The subversion log for 2013 (http://developer.r-project.org/R_svnlog_2013) on
> the R developer page hasn't been updated since September 29. I would
> appreciate the daily updates returning.
>
Sorry, my bad, with all the server switchi
Jai,
On Oct 19, 2013, at 1:37 AM, JaiReddy wrote:
> Thanks Simon.
>
> May I know how R works if two expressions come at the same time for
> evaluation. When I debug my case I found that issue was found with indexed
> values of protected items.
>
> As R is single threaded engine, I just want to
On 13-10-20 04: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:
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
On 13-10-20 6:41 PM, Jonathan Greenberg wrote:
To be clear, if I used Depends: somepackage before, and switched over to
using Imports: somepackage, I'll need to mod my code that used to have a
call to, say, somefunction to now have somepackage::somefunction, correct?
No. You need to modify bot
Jonathan,
import/importFrom directives within the NAMESPACE places the symbol(s)
within your package's namespace. They are treated exactly the same as
(non-exported) symbols your code defines.
~G
On Sun, Oct 20, 2013 at 3:41 PM, Jonathan Greenberg wrote:
> To be clear, if I used Depends: somep
On 13-10-20 4:54 PM, Jonathan Greenberg wrote:
Duncan:
Thanks -- learning something new today -- quick follow-up, will using
the import statements in the NAMESPACE, when a user goes to
install.packages(), auto-install the "dependent" packages the same way
Depends forces?
You need to list the
To be clear, if I used Depends: somepackage before, and switched over to
using Imports: somepackage, I'll need to mod my code that used to have a
call to, say, somefunction to now have somepackage::somefunction, correct?
--j
On Sun, Oct 20, 2013 at 5:34 PM, Dirk Eddelbuettel wrote:
>
> On 20 O
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...@debian.org | http://dirk.eddelbuettel.com
__
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:
> >>
> >> I'm working on an upd
On Sun, Oct 20, 2013 at 4:49 PM, Duncan Murdoch
wrote:
> 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
>> Maint
Duncan:
Thanks -- learning something new today -- quick follow-up, will using the
import statements in the NAMESPACE, when a user goes to install.packages(),
auto-install the "dependent" packages the same way Depends forces?
--j
On Sun, Oct 20, 2013 at 3:49 PM, Duncan Murdoch wrote:
> On 13-10
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
Maintainer: 'Jonathan Asher Greenberg '
Depends: includes the non-default pack
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
16 matches
Mail list logo
