I noticed the new environmentName in R 2.5.0dev. Thus I gather that
each environment has:
(1) a name
(2) a hex value
so
1. environmentName gets the name. Is there any way to set the name?
2. is there any way to get the hex value for an environment other than doing:
e - new.env()
On 1/7/2007 5:01 AM, Gabor Grothendieck wrote:
I noticed the new environmentName in R 2.5.0dev. Thus I gather that
each environment has:
(1) a name
(2) a hex value
so
1. environmentName gets the name. Is there any way to set the name?
The NEWS entry says:
o New function
On Sun, 7 Jan 2007, Duncan Murdoch wrote:
[...]
If you want
to test for whether two variables refer to the same environment, then
attach a unique label to the environments when you create them and check
the labels.
You can simply use identical(env1, env2).
--
Brian D. Ripley,
Dear Chris,
If I correctly understand what you want to do, the Rcmdr package uses the
following functions (slightly modified from original version contributed by
Philippe Grosjean) to solve a similar problem:
RcmdrEnv - function() {
pos - match(RcmdrEnv, search())
if (is.na(pos)) { #
One other comment. If I place an attribute on the environment as you
suggest that changes all uses of the environment. I cannot keep the
original environment intact and have a subobject which represents the
original environment plus the attribute. This is just one example of why
the feature
On 1/7/2007 10:01 AM, Gabor Grothendieck wrote:
One other comment. If I place an attribute on the environment as you
suggest that changes all uses of the environment.
Yes, that's exactly what you wanted, as far as I can tell. If an
environment prints as
environment: 0x0181a320
then all
What I was referring to was your suggestion to add a class and a Name
attribute to the environment. That would change all references to it.
But what I would really want to do is to leave it alone unchanged so it
can be used in its original form by other applications but for my purpose
create a
On 1/7/2007 11:31 AM, Gabor Grothendieck wrote:
What I was referring to was your suggestion to add a class and a Name
attribute to the environment.
Yes, that was clear.
Duncan Murdoch
That would change all references to it.
But what I would really want to do is to leave it alone unchanged
Anything that has 4.5 in it will always round to 4. For example 24.5 becomes
24 and 34.5 becomes 34. Or 1234567894.5 will become 1234567894.
round(4.5)
[1] 4
round(3.5)
[1] 4
Thanks,
Clint W. Stevenson
Senior Statistician
Edison Media Research
[EMAIL PROTECTED]
--please do not edit the
On 1/6/2007 10:01 PM, [EMAIL PROTECTED] wrote:
Anything that has 4.5 in it will always round to 4. For example 24.5 becomes
24 and 34.5 becomes 34. Or 1234567894.5 will become 1234567894.
round(4.5)
[1] 4
round(3.5)
[1] 4
That's behaving as documented, using banker's rounding. See the
I think we should get rid of source attributes completely,
since they are no longer needed, but your comment still
applies to source references. We should strip them when code
gets modified.
Duncan Murdoch
I would be very concerned about losing source attributes-- it would
break a lot
On 1/7/2007 6:55 PM, [EMAIL PROTECTED] wrote:
I think we should get rid of source attributes completely,
since they are no longer needed, but your comment still
applies to source references. We should strip them when code
gets modified.
Duncan Murdoch
I would be very concerned about
12 matches
Mail list logo
