[Rd] Problem using model.frame with argument subset in own function

2009-08-08 Thread Gavin Simpson
Dear List, I am writing a formula method for a function in a package I maintain. I want the method to return a data.frame that potentially only contains some of the variables in 'data', as specified by the formula. The problem I am having is in writing the function and wrapping it around model.fr

Re: [Rd] identical(0, -0)

2009-08-08 Thread Gabor Grothendieck
On Sat, Aug 8, 2009 at 10:39 AM, Prof. John C Nash wrote: > I would urge inclusion in the documentation of the +0, -0 example(s) if > there is NOT a way in R to distinguish these. There are occasions where it For single numbers try this: x <- +0 y <- -0 identical(x, y) && identical(1/x, 1/y) # FA

Re: [Rd] identical(0, -0)

2009-08-08 Thread Prof. John C Nash
I'll save space and not include previous messages. My 2 cents: At the very least the documentation needs a fix. If it is easy to do, then Ted Harding's suggestion of a switch (default OFF) to check for sign difference would be sensible. I would urge inclusion in the documentation of the +0, -

Re: [Rd] identical(0, -0)

2009-08-08 Thread Martin Maechler
> "DM" == Duncan Murdoch > on Fri, 07 Aug 2009 12:55:50 -0400 writes: DM> On 8/7/2009 11:41 AM, Martin Maechler wrote: >>> "DM" == Duncan Murdoch >>> on Fri, 07 Aug 2009 11:25:11 -0400 writes: >> DM> On 8/7/2009 10:46 AM, Martin Maechler wrote: >> >>>

Re: [Rd] Bug in nlm, found using sem; failure in several flavors (PR#13883)

2009-08-08 Thread adik
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1660387551-150661043-1249684349=:2997 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Hi

Re: [Rd] Bug in nlm, found using sem; failure in several flavors (PR#13881)

2009-08-08 Thread Adam D. I. Kramer
Hi Jeff, As mentioned in my message, I *did* replicate on another platform. One platform was running linux in a VM, the other running MacOSX, on two different physical machines. The problem did not replicate on a PowerPC box, so if it is a bug with intel chips, I think it's also appropriate t