I have isolated an error that can be reproduced by the following code.
The same thing happens in 2.8.0pat and 2.9.0dev. It looks like the
try() code is ending up in the display list, or something?
library(grid)
library(lattice)
xyplot(1:100 ~ 1:100)
test <- try(downViewport("pageAnnotationVp"), s
Hi,
If an *.Rd file documents more than one object, and each object returns
several objects, which should ideally be described in an itemized list.
When documenting single objects, I've been doing this using simple
\item(s) inside the value section, like:
\value{This function returns:
\item{1s
* On 2008-11-13 at 18:51 -0500 Duncan Murdoch wrote:
> On 12/11/2008 8:30 PM, [EMAIL PROTECTED] wrote:
>> Full_Name: Oren Cheyette
>> Version: 2.7.2
>> OS: Win XP
>> Submission from: (NULL) (64.161.123.194)
>>
>>
>> Enter the following at the R command prompt:
>>> sprintf("A %S %S %S XYZ", 1, 1, 1)
* On 2008-11-13 at 18:51 -0500 Duncan Murdoch wrote:
> On 12/11/2008 8:30 PM, [EMAIL PROTECTED] wrote:
>> Full_Name: Oren Cheyette
>> Version: 2.7.2
>> OS: Win XP
>> Submission from: (NULL) (64.161.123.194)
>>
>>
>> Enter the following at the R command prompt:
>>> sprintf("A %S %S %S XYZ", 1, 1, 1)
On 12/11/2008 6:05 PM, [EMAIL PROTECTED] wrote:
Full_Name: Peter K Dunn
Version: NA
OS: NA
Submission from: (NULL) (203.29.106.59)
Reading the manual "Writing R Extensions", the html and pdf versions both
contain important typos in Section 1.10. As an example:
An installed file named ‘CTIAT
On 12/11/2008 8:30 PM, [EMAIL PROTECTED] wrote:
Full_Name: Oren Cheyette
Version: 2.7.2
OS: Win XP
Submission from: (NULL) (64.161.123.194)
Enter the following at the R command prompt:
sprintf("A %S %S %S XYZ", 1, 1, 1);
Note the erroneous capitalized %S instead of %s and the numeric inputs
On Nov 13, 2008, at 6:11 PM, Tony Plate wrote:
Thanks for the response.
Are the problems with versioned installs fundamental, or are they
just a case of incomplete implementation and rough edges?
If the latter, would fixes be considered?
I ask because we would find versioned installs very
Thanks for the response.
Are the problems with versioned installs fundamental, or are they just a
case of incomplete implementation and rough edges?
If the latter, would fixes be considered?
I ask because we would find versioned installs very useful in
maintaining stable production systems, e
Full_Name: Oren Cheyette
Version: 2.7.2
OS: Win XP
Submission from: (NULL) (64.161.123.194)
Enter the following at the R command prompt:
> sprintf("A %S %S %S XYZ", 1, 1, 1);
Note the erroneous capitalized %S instead of %s and the numeric inputs instead
of strings. With strings there's no crash
Full_Name: Peter K Dunn
Version: NA
OS: NA
Submission from: (NULL) (203.29.106.59)
Reading the manual "Writing R Extensions", the html and pdf versions both
contain important typos in Section 1.10. As an example:
An installed file named CTIATION will be used by the citation() function. ..
A couple more comments on the \dots problem:
1. Allowing {} after \dots is unsatisfactory, because the current
parser will render the braces, i.e. 1\dots{}10 is rendered as 1..{}10.
I'd like to have enough back-compatibility that it is possible to
rewrite a man page to work in either system.
Dear list,
Thanks very much for all of the detailed responses! I am beginning to
understand how all of this can work, and learning quite a bit about
the C language in the process!
Can this be applied to either C++ classes or to member functions of a
class? Please forgive my lack of general C/C
Just one additional comment in line below:
On 11/13/2008 1:44 PM, Duncan Murdoch wrote:
On 11/13/2008 11:51 AM, Simon Urbanek wrote:
Duncan,
I had a quick look at the parsers differences and I'm worried about
points 1. and 2. (on p.6) -- does that imply that \R{} is illegal and
so is any \
On 11/13/2008 11:51 AM, Simon Urbanek wrote:
Duncan,
I had a quick look at the parsers differences and I'm worried about
points 1. and 2. (on p.6) -- does that imply that \R{} is illegal and
so is any \foo{} for any macro \foo that doesn't take any arguments?
IMHO that would be fatal (if I
Bill and Mike,
Thanks for your help. I think Mike was right about the
80-bit/64-bit compare. As Mike thought, the error occurs at a test for
equality, i.e.
if (x .ge. y) then
I know better than to test reals for equality, but this is a closed
interval test, and it still fails.
I've just committed the parse_Rd() function to R-devel. This is a
parser for Rd files, described in
http://developer.r-project.org/parseRd.pdf
It is not identical to the current parser, and about a dozen of the base
man pages currently signal syntax errors. It also detected errors in 10
fil
On Nov 12, 2008, at 23:16 , Jeff Ryan wrote:
Charles,
I've looked through the "Writing R Extensions" manual, and can't find
this documented very clearly. A previous question to the list gave
me
the very kind response pasted below. I've looked at the suggested
examples (lme4 using C functi
17 matches
Mail list logo
