similar to: identical() versus sapply()

Use all.equal instead of identical if you want to gloss over integer/numeric class differences and minor floating point differences (and a host of others). Bill Dunlap TIBCO Software wdunlap tibco.com On Mon, Apr 11, 2016 at 5:25 PM, Paulson, Ariel <apa at stowers.org> wrote: > Hi Jeff, > > > We are splitting hairs because R is splitting hairs, and causing us > problems.

Hi Jeff, We are splitting hairs because R is splitting hairs, and causing us problems. Integer and numeric are different R classes with different properties, mathematical relationships notwithstanding. For instance, the counterintuitive result: > identical(as.integer(1), as.numeric(1)) [1] FALSE Unfortunately the reply-to chain doesn't extend far enough -- here is the original

On 11/04/2016 8:25 PM, Paulson, Ariel wrote: > Hi Jeff, > > > We are splitting hairs because R is splitting hairs, and causing us problems. Integer and numeric are different R classes with different properties, mathematical relationships notwithstanding. For instance, the counterintuitive result: The issue here is that R has grown. The as() function is newer than the as.numeric()

Indeed! Slightly simplified to emphasize your point: > class(as(1:2,"numeric")) [1] "integer" > class(as.numeric(1:2)) [1] "numeric" whereas in ?as it says: "Methods are pre-defined for coercing any object to one of the basic datatypes. For example, as(x, "numeric") uses the existing as.numeric function. " I suspect this is related to

Hypothesis regarding the thought process: integer is a perfect subset of numeric, so why split hairs? -- Sent from my phone. Please excuse my brevity. On April 11, 2016 12:36:56 PM PDT, Bert Gunter <bgunter.4567 at gmail.com> wrote: >Indeed! > >Slightly simplified to emphasize your point: > >> class(as(1:2,"numeric")) >[1] "integer" > >>

Ok, I see the difference between 1 and 1:2, I'll just leave it as one of those "only in R" things. But it seems then, that as.numeric() should guarantee a FALSE outcome, yet it does not. To build on what Rolf pointed out, I would really love for someone to explain this one: > str(1) num 1 > str(1:2) int [1:2] 1 2 > str(as.numeric(1:2)) num [1:2] 1 2 >

"The documentation aims to be accurate, not necessarily clear." !!! I hope that is not the case! Accurate documentation that is confusing is not very useful. I understand that it is challenging to write docs that are both clear and accurate; but I hope that is always the goal. Cheers, Bert Bert Gunter "The trouble with having an open mind is that people keep coming along and

I highly recommend making friends with the str function. Try str( 1 ) str( 1:2 ) for the clue you need, and then sapply( 1:2, identical, 1L ) -- Sent from my phone. Please excuse my brevity. On April 8, 2016 3:24:31 PM PDT, "Paulson, Ariel" <apa at stowers.org> wrote: >Sorry if this has been answered elsewhere, but I can't find any >discussion of it. >

On 09/04/16 16:24, Jeff Newmiller wrote: > I highly recommend making friends with the str function. Try > > str( 1 ) > str( 1:2 ) Interesting. But to me counter-intuitive. Since R makes no distinction between scalars and vectors of length 1 (or more accurately I think, since in R there is *no such thing as a scalar*, only a vector of length 1) I don't see why "1"

On 11/04/2016 10:18 PM, Bert Gunter wrote: > "The documentation aims to be accurate, not necessarily clear." > > !!! > > I hope that is not the case! Accurate documentation that is confusing > is not very useful. I don't think it is ever intentionally confusing, but it is often concise to the point of obscurity. Words are chosen carefully, and explanations are

> -----Original Message----- > From: bgunter.4567 at gmail.com > Sent: Mon, 11 Apr 2016 19:18:39 -0700 > To: murdoch.duncan at gmail.com > Subject: Re: [R] [FORGED] Re: identical() versus sapply() > > "The documentation aims to be accurate, not necessarily clear." > > !!! > > I hope that is not the case! Accurate documentation that is confusing > is

Thank you Rolf. fortune(350) was the link I was trying to remember. I believe! I believe in the documentation. It can be incredibly difficult to document something and unless one has an editor to read and 'try' to interpret the results the original writer may not realise just how opaque the explanation is. John Kane Kingston ON Canada > -----Original Message----- > From:

I just compile one kernel to the domU but cant see the PCI netcard, i hide the card from dom0 physdev_dom0_hide=''(00:11.0)'' and added to the domU config pci = [ ''0,11,0'' ] and dint work.. any howto to do that? - ariel ariel en BSDlatino . org ariel en ferreras . info http://www.BSDlatino.org http://ariel.BSDlatino.org

Hi All, I need to evaluate a series expansion using Legendre polynomials. Using the 'orthopolinom' package I can get a list of the first n Legendre polynomials as character strings. > library(orthopolynom) > l<-legendre.polynomials(4) > l [[1]] 1 [[2]] x [[3]] -0.5 + 1.5*x^2 [[4]] -1.5*x + 2.5*x^3 [[5]] 0.375 - 3.75*x^2 + 4.375*x^4 But I can't figure out how to

I just can't get kphone to register with asterisk, i can make calls to the demos and even get into the mailbox but kphone cannot register. Here's my story. Can you help me?? Please I have installed asterisk on debian using apt-get install asterisk. I have configured an extension in extensions.conf as follows exten => 8003,1,Dial(Sip/8003,${RINGTIME},rt) exten =>

On 12/04/16 14:45, Duncan Murdoch wrote: > On 11/04/2016 10:18 PM, Bert Gunter wrote: >> "The documentation aims to be accurate, not necessarily clear." >> >> !!! >> >> I hope that is not the case! Accurate documentation that is confusing >> is not very useful. > > I don't think it is ever intentionally confusing, but it is often >

On 11/04/2016 11:34 PM, Rolf Turner wrote: > On 12/04/16 14:45, Duncan Murdoch wrote: >> On 11/04/2016 10:18 PM, Bert Gunter wrote: >>> "The documentation aims to be accurate, not necessarily clear." >>> >>> !!! >>> >>> I hope that is not the case! Accurate documentation that is confusing >>> is not very useful. >>

Anyone, can you say what was the reason to rename bytecode? I am still interesting in 2010/9/29 Duncan Sands <baldrick at free.fr> Hi Ariel, > As long as I know English the word "bit" is a "small pice", . Why in set of > documentation ir is "bytecode", in other set or llvm source is "bitecode"? > What is the right? Different people call the

Hollo I'm new, My name is Ariel Arelovich I've encountered the following problem trying to sue metaflac. I used the following command: c:\Archivos de programa\FLAC>metaflac --set-tag-from-file="CUESHEET=sola.cue" so la.flac sola.flac: ERROR: file 'sola.cue' for 'CUESHEET' tag value has embedded NULs And I've got that error. See I have the flac that is

On 12/04/2016 9:21 AM, ProfJCNash wrote: > >>>> "The documentation aims to be accurate, not necessarily clear." > > I notice that none of the critics > > in this thread have offered improvements on what is there. > > > This issue is as old as documented things. With software it is > particularly nasty, especially when we want the software to