search for: getbinding

I was reading up on ERB documentation and a snippet on rhtml requiring the use of Object.get_binding caught my attention: ... rhtml = ERB.new("someTemplate") rhtml.run(someObject.get_binding) ... Curious about tools I have at my disposal to learn more about things I don''t know about Ruby, i typed the following into my DOS console: ri get_binding and got the following

...course (name >>> objects) but they do not provide access to the value, which is typically >>> R_UnboundValue. But this does not even need to be implemented with SYMSXP. >>> The design would allow something like: >>> >>> binding <- getBinding("x", env) >>> if (hasValue(binding)) { >>> x <- value(binding) # throws an error if none >>> message(name(binding), "has value", x) >>> } >>> >>> That I think it is a bit verbose but readable a...

...e already have SYMSXPs at the R level of course (name >> objects) but they do not provide access to the value, which is typically >> R_UnboundValue. But this does not even need to be implemented with SYMSXP. >> The design would allow something like: >> >> binding <- getBinding("x", env) >> if (hasValue(binding)) { >> x <- value(binding) # throws an error if none >> message(name(binding), "has value", x) >> } >> >> That I think it is a bit verbose but readable and could be made fast. And >> I >> thin...

...cture that points to the name and a value. We already have SYMSXPs at the R level of course (name objects) but they do not provide access to the value, which is typically R_UnboundValue. But this does not even need to be implemented with SYMSXP. The design would allow something like: binding <- getBinding("x", env) if (hasValue(binding)) { x <- value(binding) # throws an error if none message(name(binding), "has value", x) } That I think it is a bit verbose but readable and could be made fast. And I think binding objects would be useful in other ways, as they are essentia...

...> and a value. We already have SYMSXPs at the R level of course (name > objects) but they do not provide access to the value, which is typically > R_UnboundValue. But this does not even need to be implemented with SYMSXP. > The design would allow something like: > > binding <- getBinding("x", env) > if (hasValue(binding)) { > x <- value(binding) # throws an error if none > message(name(binding), "has value", x) > } > > That I think it is a bit verbose but readable and could be made fast. And I > think binding objects would be useful in...

In November, we had a "bug repository conversation" with Peter Hagerty and myself: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16065 where the bug report title started with --->> "exists" is a bottleneck for dispatch and package loading, ... Peter proposed an extra simplified and henc faster version of exists(), and I commented > --- Comment #2