Is there a reason why the fix for Bug 15899 - Omitted 'extern' on
'R_running_as_main_program' after refactor can cause linker errors for
applications embedding R...
https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=15899
was never back ported for R 3.3 for the R 3.2.1 release? Restoring
th
Millot,
On Mon, Jun 15, 2015 at 9:19 AM, Hadley Wickham wrote:
> Regardless of the value of the other arguments, the first element in
> the output of seq() is _always_ `from`.
>
Indeed, as Hadley says, the output of seq must always start with* from*. It
is a sequence starting at *from* and end
You're not the first one, e.g.
https://stat.ethz.ch/pipermail/r-devel/2010-March/057029.html
https://stat.ethz.ch/pipermail/r-devel/2010-November/058981.html
(I was bitten by this in a resampling scheme where the set sampled
from was data driven).
Here's a simple solution - taken from R.utils::r
Regardless of the value of the other arguments, the first element in
the output of seq() is _always_ `from`.
Hadley
On Mon, Jun 15, 2015 at 9:56 AM, Millot Gael wrote:
> Thanks for your answer.
>
> The rational behind my proposal is why taking "from" when length.out=1, more
> than "to" or "NA",
Thanks for your answer.
The rational behind my proposal is why taking "from" when length.out=1, more
than "to" or "NA", or " integer(0) " ?
This question seems basic. But is is not in certain situations, like when
length.out = unpredictable positive integer.
And I haven't found in ?seq() the p
> Radford Neal
> on Mon, 15 Jun 2015 10:11:33 -0400 writes:
>> > The current R release candidate has a lack of protect bug
>> > (of very long standing)
>>
>> [ but not really reported, right ? ]
> It's "long standing" because it exists in versions of R going
Millot,
I think the problem with that is that what you propose isn't a sequence
starting at from in any meaningful way, and thus does not satisfy the
contract of the seq function.
Best,
~G
On Jun 15, 2015 7:12 AM, "Millot Gael" wrote:
> Hi.
>
> I have a problem with the default behavior of seq
Hi.
I have a problem with the default behavior of seq(), which gives the argument
"from" when the argument length.out = 1.
This behavior is annoying when the number of value determine in length.out is
not predictable.
Would it be possible to add an argument that propose the median/mean, i.e.
(f
> > The current R release candidate has a lack of protect bug
> > (of very long standing)
>
> [ but not really reported, right ? ]
It's "long standing" because it exists in versions of R going
back many years.
> but the R 3.2.1 release candidate probably really cannot be
> touched no
Hi.
I have a problem with the default behavior of sample(), which performs
sample(1:x) when x is a single value.
This behavior is well explained in ?sample.
However, this behavior is annoying when the number of value is not predictable.
Would it be possible to add an argument
that desactivates t
> Radford Neal
> on Sat, 13 Jun 2015 17:24:04 -0400 writes:
> The current R release candidate has a lack of protect bug
> (of very long standing)
[ but not really reported, right ? ]
> with respect to the
> R_print.na_string and R_print.na_string_noquote fields of
11 matches
Mail list logo