On 10/09/2021 12:53, brodie gaslam wrote:
On Friday, September 10, 2021, 03:13:54 PM EDT, Hervé Pagès
wrote:
Good catch, thanks!
Replacing
if(ISNAN(vi) || (tmp = (int) vi) < 0 || tmp > 255) {
tmp = 0;
warn |= WARN_RAW;
}
pa[i] = (Rbyte) tmp;
with
> On Friday, September 10, 2021, 03:13:54 PM EDT, Hervé Pagès
> wrote:
>
> Good catch, thanks!
>
> Replacing
>
> if(ISNAN(vi) || (tmp = (int) vi) < 0 || tmp > 255) {
> tmp = 0;
>
> warn |= WARN_RAW;
>
> }
> pa[i] = (Rbyte) tmp;
>
> with
>
> if(ISNAN(vi) || vi <=
On 10/09/2021 09:12, Duncan Murdoch wrote:
On 10/09/2021 11:29 a.m., Hervé Pagès wrote:
Hi,
The first warning below is unexpected and confusing:
> as.raw(c(3e9, 5.1))
[1] 00 05
Warning messages:
1: NAs introduced by coercion to integer range
2: out-of-range values treate
ange [0 to 255] BEFORE converting to an integer.
--
Sincerely
Andr� GILLIBERT
De : R-devel de la part de Duncan Murdoch
Envoy� : vendredi 10 septembre 2021 18:12:02
� : Herv� Pag�s; r-devel
Objet : Re: [Rd] Spurious warnings in coercion from double/complex/cha
On 10/09/2021 11:29 a.m., Hervé Pagès wrote:
Hi,
The first warning below is unexpected and confusing:
> as.raw(c(3e9, 5.1))
[1] 00 05
Warning messages:
1: NAs introduced by coercion to integer range
2: out-of-range values treated as 0 in coercion to raw
The reason we get it
Hi,
The first warning below is unexpected and confusing:
> as.raw(c(3e9, 5.1))
[1] 00 05
Warning messages:
1: NAs introduced by coercion to integer range
2: out-of-range values treated as 0 in coercion to raw
The reason we get it is that coercion from numeric to raw is currently
impl
