Thanks very much for the patches. I have spent a couple of days
working through them, and others have looked at some of them as well
and may continue to do so. Here are some notes on the individual
patches describing things I have done or decided not to do and things
others have done that I know
It crashes R on my linux:
> regexpr("a{2-}", "")
R: tre-compile.c:1825: tre_ast_to_tnfa: Assertion `iter->max == -1 ||
iter->max == 1' failed.
Aborted
My setup is:
> sessionInfo()
R version 2.11.1 (2010-05-31)
i386-redhat-linux-gnu
locale:
[1] LC_CTYPE=en_NZ LC_NUMERIC=C LC_TI
Le 22/09/10 17:31, Duncan Murdoch a écrit :
On 22/09/2010 11:22 AM, Karl Forner wrote:
Thanks Duncan for your suggestion.
I could not find any package using dynamic library, namespaces and not
the
useDynLib pragma so
I created a minimalistic package to demonstrate the problem.
Please find atta
[Accidentally posted this to r-help instead of r-devel; reposting to put
it into the correct list and thread. My apologies for the duplication.]
On 9/21/2010 8:04 PM, Henrik Bengtsson wrote:
Each of the following calls crash ("core dumps") R (R --vanilla) on
various versions and OSes:
regexpr(
> Your package depends on Rcpp, so I didn't try it in the alpha version of
2.12.0
It's a mistake, in fact it does not depend anymore. You can safely delete
the src/Makevars file.
Duncan Murdoch
>
>
> Steps to reproduce the problem:
>>
>> * unarchive it ( tar zxvf foo_0.1.tar.gz )
>> * cd foo
>>
On 22/09/2010 11:22 AM, Karl Forner wrote:
Thanks Duncan for your suggestion.
I could not find any package using dynamic library, namespaces and not the
useDynLib pragma so
I created a minimalistic package to demonstrate the problem.
Please find attached a very small package foo (8.8k)
Your p
Thanks Duncan for your suggestion.
I could not find any package using dynamic library, namespaces and not the
useDynLib pragma so
I created a minimalistic package to demonstrate the problem.
Please find attached a very small package foo (8.8k)
Steps to reproduce the problem:
* unarchive it ( tar
On Wed, 22 Sep 2010, carol white wrote:
So there is no sort of automatic way like using a markup command for the
susceptible fields instead of splitting manually a line on different lines?
Well, how is the automatic command to know how to do this? As you
will see from the autmatic wrapping
So there is no sort of automatic way like using a markup command for the
susceptible fields instead of splitting manually a line on different lines?
True that this doesn't happen in Arguments field (I confused with Format
field).
Also true that the codes used in Usage, Examples etc are in cou
On Tue, 14 Sep 2010, Ben Bolker wrote:
Under the description of the 'type' argument, ?residuals.gls says
'Defaults to ‘"pearson"’.'
But residuals.gls starts
residuals.gls <-
function(object, type = c("response", "pearson", "normalized"), ...)
{
type <- match.arg(type)
...
which sure looks t
On Wed, 22 Sep 2010, carol white wrote:
Thank you very much Uwe. It works now.
I have a question about pdf formating in pdf manual file:
How to format the long lines which go to the margin? For ex, this
happens in Usage field if a function has many arguments. Also, it
happens in examples or
Thank you very much Uwe. It works now.
I have a question about pdf formating in pdf manual file:
How to format the long lines which go to the margin? For ex, this happens in
Usage field if a function has many arguments. Also, it happens in examples or
Arugment sections when the lines are long.
For what concerns emacs users, the number of '#' has different effects
on the position of the comment. From the ESS manual: 'By default,
comments beginning with ‘###’ are aligned to the beginning of the
line. Comments beginning with ‘##’ are aligned to the current level of
indentation for the block
13 matches
Mail list logo
