I would like to follow up on another one of the documentation issues raised in
the discussion on function hints. Duncan mentioned that the R core were working
on preprocessing directives for .Rd files, which could possibly include some
sort of include directive. I was wondering if a
On 19 Jun 2006, at 12:45, Gabor Grothendieck wrote:
Try this:
both - c(x,y)
as.table(tapply(both, names(both), sum))
thanks for this, Gabor.
The class of the objects I am manipulating in my
package is c(count, table).
It'd be nice to overload the + symbol so that I can add
two count
Dear R core,
influenced by recent panel discussion in Vienna I think that it would be
nice to add package specific output of citation() function to package
reference manuals. I think that apropriate place would be just after
fields from DESCRIPTION file. This will be OK for CRAN, but not for
On 6/20/2006 5:18 AM, Heather Turner wrote:
I would like to follow up on another one of the documentation issues raised
in the discussion on function hints. Duncan mentioned that the R core were
working on preprocessing directives for .Rd files, which could possibly
include some sort of
On 6/20/06, Robin Hankin [EMAIL PROTECTED] wrote:
On 19 Jun 2006, at 12:45, Gabor Grothendieck wrote:
Try this:
both - c(x,y)
as.table(tapply(both, names(both), sum))
thanks for this, Gabor.
The class of the objects I am manipulating in my
package is c(count, table).
It'd be nice
On Tue, 20 Jun 2006 12:22:42 +0200 (CEST),
gregor gorjanc (gg) wrote:
Dear R core,
influenced by recent panel discussion in Vienna I think that it would be
nice to add package specific output of citation() function to package
reference manuals. I think that apropriate place would be
I think it's bad to document dissimilar functions in the same file, but
similar related functions *should* be documented together. Not doing
this just adds to the burden of documenting them, and the risk of
modifying only part of the documentation so that it is inconsistent.
The user also gets
For me, it's been extremely helpful to keep function documentation
together during editing-- it greatly increases the chance that I will
actually update the doco when I change the code, rather than putting it
off until I've forgotten what I did. Also, writing Rd format is a
nightmare (again,
find . -name *.Rd | xargs grep who's
these should both be whose
./src/library/base/man/which.Rd: a \code{\link{dim}} attribute), the
result is a matrix who's rows each
(also consider whose rows are each the indices ... rather than
whose rows each are the indices ...)
