The MKsetup() in unique.c throws an error if the vector to be hashed is
longer than (2^32)/8:
if(n < 0 || n > 536870912) /* protect against overflow to -ve */
error(_("length %d is too large for hashing"), n);
I occasionally work with vectors longer than this on 64-bit builds. Would i
On 13/01/2010 6:15 PM, Ross Boylan wrote:
I'm having trouble getting correct help output in some circumstances for
a package I've created. Though this is not an issue with the current R,
I would like my package to work with previous ones as well.
I'm looking for suggestions about how I could rew
Yes, a bug prevented callNextMethod() from detecting the special case of
the `[` call, for which it did have code.
Should be fixed in the current 2.11.0 (r 50976).
Thanks for the helpful bug report.
John Chambers
bernd_bis...@gmx.net wrote:
Hi,
there seems to be a possible bug in callNextMe
I'm having trouble getting correct help output in some circumstances for
a package I've created. Though this is not an issue with the current R,
I would like my package to work with previous ones as well.
I'm looking for suggestions about how I could rework my .Rd file so that
it will work with pr
WinXP, R version 2.10.1:
> s1<- strftime("2009/12/15 11:55:00 PM", format="%Y/%m/%d %I:%M:%S %p",
> tz="GMT", usetz=FALSE)
> print(s1)
[1] "2009/12/15 11:55:00 AM"
> s2<- strftime("2009/12/16 12:00:00 AM", format="%Y/%m/%d %I:%M:%S %p",
> tz="GMT", usetz=FALSE)
> print(s2)
[1] "2009/12/16 12:00
Hi,
there seems to be a possible bug in callNextMethod in conjunction with
the [-operator.
Relevant info, minimal example and sessionInfo follow below:
###
setClass("foo", representation = representation(a = "numeric"))
setClass("bar", contains = "foo")
setMethod(
Going back a few months
I also thought "it would be nice if R had built into it some way of running
code in source packages possibly with degraded functionality to ease
development"
so building on Barry Rowlingsons start I came up with this:
---
loadDir <- function(.Ro
2010/1/11 Jens Oehlschlägel :
> Petr,
> This can have severe consequences like accessing beyond the limits of an
> array. If C-code is involved, this can crash R. In the worst case algorithms
> can silently do wrong. Being an admirer of R since its early days, I was
> shocked to see this, and as
2010/1/12 Simon Urbanek
> Even worse, this is a known bug long fixed in R 2.10.1 and hence a doubly
> pointless report ...
> Cheers,
> Simon
>
>
> You're right... have not seen that my daughter has a more recent version.
Download 2.10.1 from KUL-Leuven mirror on my G5 and all is fine: you can
clo
