Displaying 8 results from an estimated 8 matches for "fulfulling".
Did you mean:
fulfilling
2023 Nov 06
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...ng "dilemma" that nobody can help us with is that
"almost infinitely" many different complex numbers z fulfill
is.na(z) |--> TRUE
and only one of them is NA_complex_ and that may be unintuitive.
OTOH, we already have for the doubles that there are at least two
different x fulfulling is.na(x), namely NaN and NA
and from C's point of view there are even considerably more
different NaN's .. but now I'm definitely digressing.
Martin
2023 Nov 07
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...obody can help us with is that
> "almost infinitely" many different complex numbers z fulfill
> is.na(z) |--> TRUE
> and only one of them is NA_complex_ and that may be unintuitive.
>
> OTOH, we already have for the doubles that there are at least two
> different x fulfulling is.na(x), namely NaN and NA
> and from C's point of view there are even considerably more
> different NaN's .. but now I'm definitely digressing.
>
> Martin
>
[[alternative HTML version deleted]]
2023 Nov 08
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...y different complex numbers z fulfill
> >> is.na(z) |--> TRUE
> >> and only one of them is NA_complex_ and that may be unintuitive.
> >>
> >> OTOH, we already have for the doubles that there are at least two
> >> different x fulfulling is.na(x), namely NaN and NA
> >> and from C's point of view there are even considerably more
> >> different NaN's .. but now I'm definitely digressing.
> >>
> >> Martin
> >>
2023 Nov 09
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...plex numbers z fulfill
>> >> is.na(z) |--> TRUE
>> >> and only one of them is NA_complex_ and that may be unintuitive.
>> >>
>> >> OTOH, we already have for the doubles that there are at least two
>> >> different x fulfulling is.na(x), namely NaN and NA
>> >> and from C's point of view there are even considerably more
>> >> different NaN's .. but now I'm definitely digressing.
>> >>
>> >> Martin
>> >>
2014 Jan 14
2
USB boot problems on Gigabyte GA-M55Plus-S3G
In message <CAD0Rxe=p2gHHN9U3Zjn34Y71-KTxk5v+WzG7V3VH0ZNGCzqSvA at mail.gmail.com>
Gene Cumm <gene.cumm at gmail.com> wrote:
>On Fri, Jan 10, 2014 at 9:35 PM, Ronald F. Guilmette
><rfg at tristatelogic.com> wrote:
>> In message <BLU0-SMTP145A44932CB6CC2DB4621568BB30 at phx.gbl>,
>> Ady <ady-sf at hotmail.com> wrote:
>
>>>I don't know
2023 Nov 05
2
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
This is another follow-up to the thread from September "Recent changes to
as.complex(NA_real_)".
A test in data.table was broken by the changes for NA coercion to complex;
the breakage essentially comes from
c(NA, 0+1i)
# vs
c(as.complex(NA), 0+1i)
The former is the output we tested against; the latter is essentially (via
coerceVector() in C) what's generated by our
2014 Jan 11
2
USB boot problems on Gigabyte GA-M55Plus-S3G
In message <BLU0-SMTP145A44932CB6CC2DB4621568BB30 at phx.gbl>,
Ady <ady-sf at hotmail.com> wrote:
>> Is there something specific I should try? /boot/syslinux ?
>>
>
>>From the syslinux boot prompt in UBCD you could try:
>/boot/syslinux/config.c32 /boot/syslinux/syslinux.cfg /boot/syslinux/
>
>(Yes, it is the same basic absolute path, three times, all
2006 Mar 21
1
weird bugs with mmap-ing via NFS
[Moved from -current to -stable]
???????? 21 ???????? 2006 16:23, Matthew Dillon ?? ????????:
> ? ? You might be doing just writes to the mmap()'d memory, but the system
> ? ? doesn't know that.
Actually, it does. The program tells it, that I don't care to read, what's
currently there, by specifying the PROT_READ flag only.
> ? ? The moment you touch any mmap()'d