From bibiko at eva.mpg.de  Mon Dec 19 12:43:01 2011
From: bibiko at eva.mpg.de (=?iso-8859-1?Q?Hans-J=F6rg_Bibiko?=)
Date: Mon, 19 Dec 2011 12:43:01 +0100
Subject: [Rd] Possible bug in edit(x) for editing matrices [tested on a
	Mac]
In-Reply-To: <4EEF1E8A.2020206@stats.ox.ac.uk>
References: <2749EBD6-2786-4E5C-BC58-7B8AE4177AE4@eva.mpg.de>
	<4EEF1E8A.2020206@stats.ox.ac.uk>
Message-ID: <1667C8DD-320B-437D-97DC-A5DD7EF19D35@eva.mpg.de>


On 19 Dec 2011, at 12:22, Prof Brian Ripley wrote:

>> it seems there's a possible bug in edit(x) if x is a matrix filled with NA only.
> 
> It's as documented.  Hint: look at mode(a) or str(a), and check what values are accepted for a logical matrix.

Thank you very much! I wasn't aware of the circumstance that mode(matrix()) of course returns 'logical'. Maybe one could warn the user in the function "edit(x)" that if (is.matrix(x) && is.logical(x) == TRUE) that edit(x) doesn't work since my workaround was that I created a matrix of the dimension 10x20 via matrix(NA, nrow=10, ncol=20) and used the GUI data editor to fill the matrix's cells with values.

Kind regards,
--Hans


[Rd] Possible bug in edit(x) for editing matrices [tested on a Mac]
=?iso-8859-1?Q?Hans-J=F6rg_Bibiko?=