Hello:
What do you suggest I do to overcome "LaTeX Error: File
'inconsolata.sty' not found", which I got running "R CMD check" on a
package using Rtools I downloaded yesterday?
I found a similar question to R-Help Nov. 3 (URL below), but I've not
yet had success in replicating the s
The key point here is that setGeneric("unique") is done that way,
without other argument, whoever does it. That creates the generic from
the implicit generic corresponding to base::unique. If package A had
done anything else, the resulting methods tables would NOT refer to
package "base" but
On 11-12-16 5:29 PM, Terry Therneau wrote:
Yes, it was glaring and obvious: I had the label "description" a second
time when I really meant "details".
Still, I had to delete sections of the file 1 by 1 until it slapped me
in the face. Sorry for any bother.
Thanks. The error report looks bug
On 12/16/2011 12:19 PM, John Chambers wrote:
The subject heading is correct if referring to exportMethods() and
importMethodsFrom(). They refer to the methods tables, not the generic
functions, whatever the extensions manual says.
Looking into the code of namespaceImportMethods() will illustrate
Yes, it was glaring and obvious: I had the label "description" a second
time when I really meant "details".
Still, I had to delete sections of the file 1 by 1 until it slapped me
in the face. Sorry for any bother.
Terry T.
__
R-devel@r-project.org
I get the following error from one of my Rd files in R CMD check (R
2-14.0)
* checking Rd files ... WARNING
Error in switch(attr(block, "Rd_tag"), TEXT = if (!grepl("^[[:space:]]*
$", :
EXPR must be a length 1 vector
problem found in ‘backsolve.Rd’
This is likely something that will be glari
The subject heading is correct if referring to exportMethods() and
importMethodsFrom(). They refer to the methods tables, not the generic
functions, whatever the extensions manual says.
Looking into the code of namespaceImportMethods() will illustrate this.
It just deals with lists of metho
Michael,
meanwhile the "bibentry" class that Kurt mentioned back in the discussion
in 2010 is fully implemented in R. Hence the code can be simplified when
working with the "bibentry" objects directly (instead of the "Bibtex"
objects derived from them).
I've quickly hacked some code to illus
tar of Pkgs A, B, C attached. Martin
On 12/15/2011 03:34 PM, Martin Morgan wrote:
In
> R.version.string
[1] "R Under development (unstable) (2011-12-15 r57901)"
section 1.6.6 of 'Writing R Extensions' says
Note that exporting methods on a generic in the namespace will
also export the generic
On 12/16/2011 02:02 AM, Martin Maechler wrote:
On 12/15/2011 03:40 PM, Martin Morgan wrote:
In
> R.version.string
[1] "R Under development (unstable) (2011-12-15 r57901)"
PkgA promotes 'unique' to a generic and exports that
DESCRIPTION:
Imports: methods
R/f.R:
setGeneric("unique")
NAMESP
Back in 2010 I raised this issue, and there was some discussion,
https://stat.ethz.ch/pipermail/r-devel/2010-November/058987.html
The goal, then, as now is to have a way to produce a bibtex-clean .bib
file (i.e., not requiring
manual editing except in unusual circumstances) reflecting installed
This is also something I'd appreciate for the devtools package.
Hadley
On Fri, Dec 16, 2011 at 7:36 AM, Daniel Adler wrote:
> Dear R Core Team,
>
> I have a question related to the programming interface for namespace object
> creation at run-time.
>
> This is something that I need in the rdyncal
Dear R Core Team,
I have a question related to the programming interface for namespace object
creation at run-time.
This is something that I need in the rdyncall package:
During the dynamic linkage binding of a shared C library, an R namespace object
is created
that gets populated with call wr
Thanks to all!
Nicola
2011/12/16 Martin Maechler
> > David Scott
> > on Fri, 16 Dec 2011 22:51:11 +1300 writes:
>
>> One easy way is to list the undocumented files in
>> pkg-internal.Rd. From the Writing R Extensions manual:
>
>> Note that all user-level objects in a pa
> David Scott
> on Fri, 16 Dec 2011 22:51:11 +1300 writes:
> One easy way is to list the undocumented files in
> pkg-internal.Rd. From the Writing R Extensions manual:
> Note that all user-level objects in a package should be
> documented; if a package pkg contains us
> On 12/15/2011 03:40 PM, Martin Morgan wrote:
> > In
> >
> > > R.version.string
> > [1] "R Under development (unstable) (2011-12-15 r57901)"
> >
> > PkgA promotes 'unique' to a generic and exports that
> >
> > DESCRIPTION:
> > Imports: methods
> >
> > R/f.R:
> > setGeneric("unique")
> >
> > NAMES
One easy way is to list the undocumented files in pkg-internal.Rd. From
the Writing R Extensions manual:
Note that all user-level objects in a package should be documented; if a
package pkg contains user-level objects which are for “internal” use
only, it should provide a file pkg-internal.Rd
17 matches
Mail list logo
