Hi,
On Tuesday 31 May 2011, luke-tier...@uiowa.edu wrote:
Yes you should. Changing things in other people's packages is not a
safe thing to do.
sorry to insist, but I was hoping for a slightly more specific pointer. I'll
try asking it another way:
Suppose I was using assignInNamespace()
On Wed, 1 Jun 2011, Thomas Friedrichsmeier wrote:
Hi,
On Tuesday 31 May 2011, luke-tier...@uiowa.edu wrote:
Yes you should. Changing things in other people's packages is not a
safe thing to do.
sorry to insist, but I was hoping for a slightly more specific pointer. I'll
try asking it
On Tue, 31 May 2011, Romain Francois wrote:
Hello,
assignInNamespace refuses to assign an object to a name that is not already
used in the namespace.
That's intentional, and as documented:
‘assignInNamespace’ and ‘fixInNamespace’ are invoked for their
side effect of changing the
On Tue, 31 May 2011, Prof Brian Ripley wrote:
On Tue, 31 May 2011, Romain Francois wrote:
Hello,
assignInNamespace refuses to assign an object to a name that is not already
used in the namespace.
That's intentional, and as documented:
‘assignInNamespace’ and ‘fixInNamespace’ are
Le 31/05/11 12:01, Prof Brian Ripley a écrit :
On Tue, 31 May 2011, Prof Brian Ripley wrote:
On Tue, 31 May 2011, Romain Francois wrote:
Hello,
assignInNamespace refuses to assign an object to a name that is not
already used in the namespace.
That's intentional, and as documented:
Also note at the beginning of of th help file:
Utility functions to access and replace the non-exported functions
in a name space, for use in developing packages with name spaces.
^^
This is intended only as a developer convenience,
On Tuesday 31 May 2011, luke-tier...@uiowa.edu wrote:
Also note at the beginning of of th help file:
Utility functions to access and replace the non-exported functions
in a name space, for use in developing packages with name spaces.
On Tue, 31 May 2011, Thomas Friedrichsmeier wrote:
On Tuesday 31 May 2011, luke-tier...@uiowa.edu wrote:
Also note at the beginning of of th help file:
Utility functions to access and replace the non-exported functions
in a name space, for use in developing packages with name
Thomas,
On May 31, 2011, at 2:16 PM, Thomas Friedrichsmeier wrote:
On Tuesday 31 May 2011, luke-tier...@uiowa.edu wrote:
Also note at the beginning of of th help file:
Utility functions to access and replace the non-exported functions
in a name space, for use in developing
On Tuesday 31 May 2011, Simon Urbanek wrote:
I would expect so, but I'll let Luke comment on it. It is definitely a very
bad idea.
R provides facilities for customization and other GUIs are using them
properly. If you are lacking anything, I would suggest asking here first -
it is much
10 matches
Mail list logo
