[Martin Maechler]
>Hence --- for back compatibility reasons -- I now tend to agree
>with Duncan Murdoch, and would not change xy.coords() behavior
>at all, but simply amend the documentation.
It's fine, thanks a lot.
--
François Pinard http://pinard.progiciels-bpi.ca
> "FrPi" == François Pinard <[EMAIL PROTECTED]>
> on Mon, 5 Jun 2006 08:11:20 -0400 writes:
FrPi> [Martin Maechler]
>> Thanks a lot, Francois, for your careful reading and
>> careful report!
FrPi> Thanks for being receptive! :-)
FrPi> Another problem in the same a
[Martin Maechler]
> Thanks a lot, Francois, for your careful reading and careful report!
Thanks for being receptive! :-)
>FrPi> Another problem in the same area: the documentation lies
>FrPi> about how the function acts when given a data.frame. From
>FrPi> the code, a data.frame is
On 6/5/2006 5:30 AM, [EMAIL PROTECTED] wrote:
>> "FrPi" == François Pinard <[EMAIL PROTECTED]>
>> on Sun, 4 Jun 2006 06:27:53 +0200 (CEST) writes:
>
> FrPi> Hi, people.
> FrPi> xy.coords() does not behave like its documentation says, when given
> some
> FrPi> matrices.
> "FrPi" == François Pinard <[EMAIL PROTECTED]>
> on Sun, 4 Jun 2006 06:27:53 +0200 (CEST) writes:
FrPi> Hi, people.
FrPi> xy.coords() does not behave like its documentation says, when given
some
FrPi> matrices. ?xy.coords says:
FrPi> If 'y' is 'NULL' and 'x' is a
Hi, people.
xy.coords() does not behave like its documentation says, when given some
matrices. ?xy.coords says:
If 'y' is 'NULL' and 'x' is a [...] formula [...] list [...]
time series [...] matrix with two columns [...]
In any other case, the 'x' argument is coerced to a vector
