search for: fulfull

...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

...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]]

...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 > >>

...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 >> >>

...e assumption that I have some flavor of Linux all set up and ready to run on this specific box (i.e. the one containg the Gigabyte GA-M55Plus-S3G motherboard). I don't, actually. But I may have, in future. Would that help in some way? Also, on the off chance that I might be in a position to fulfull your request for the above specific info sometime in the near future, could you please elaborate and let me know if, by "/dev/sda" in the above, you intentionally were intendeding to obtain information about the primary (sATA) hard drive in the system, and *not* about any USB-attached dev...

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

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

[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