| To: | "S-News (E-mail)" <s-news@lists.biostat.wustl.edu> |
|---|---|
| Subject: | strange all.equal() behavior |
| From: | "Mann, Brad" <Brad.Mann@citadelgroup.com> |
| Date: | Thu, 30 May 2002 11:43:30 -0500 |
Hello. I'm running S-Plus 6.0, rel 4 on NT. When I try all.equal( 8, 4 ) I get the correct answer of a 50% relative difference, but when I try all.equal( as.single(8) , 4 ) I get the seemingly incorrect and certainly unintuitive value T. Is this a bug, or are there some subtleties with int/single/double's and all.equal()? Thanks for any info, Brad |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Area under the curve, Petr Pikal |
|---|---|
| Next by Date: | Re: strange all.equal() behavior, Bob Baskin |
| Previous by Thread: | Call for Workshop Proposals (IEEE Data Mining 2002), icdm02 |
| Next by Thread: | Re: strange all.equal() behavior, Bob Baskin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |