Dear Bill,
I didn't realize that "x." would be partially matched by "x" when there was
a first (unnamed) argument in the function call -- but I see the error now.
Thanks,
John
John Fox
Department of Sociology
McMaster University
Hamilton, Ontario
Canada L8S 4M4
Hi John,
Unfortunately I don't think that will fix it because of partial matching.
(That would be OK if the argument sequence were reversed to:
function(..., x.)
since partial matching does not occur with arguments coming after ..., but it
would break ALL existing code.)
Bill.
-O
Dear Peter and Bill,
How about changing the current "x argument to something like "x."? That
should make the problem that Bill points out less likely and still be
backwards compatible with using "x" in the call to transform().
Regards,
John
John Fox
Department o
Full_Name: Shane Neph
Version: 2.2.1
OS: mac os x
Submission from: (NULL) (71.113.43.247)
While I found the names of the package authors and maintainer, I was
unsuccessful in finding any contact information.
The preliminary documentation for heatmap.2 is inconsistent in at least a couple
of plac
<[EMAIL PROTECTED]> writes:
> If you would like a 10 second R puzzle, you might like to think about
> this one:
>
>
> > g <- expand.grid(long = 130:140, lat = -(10:25))
> > gp <- transform(g, x = long, y = lat)
> Error in transform(g, x = long, y = lat) :
> object "long" not found
>
>
