On Thu, May 16, 2013 at 6:06 AM, McGehee, Robert <
robert.mcge...@geodecapital.com> wrote:
> Duncan, Thank you for the clarification on how delayedAssign works. Should
> R-level interfaces to promise objects ever become available, I expect they
> would at time come in handy.
>
> On the subject of
Thank you for the elaborate response. I am going to look into the quartz code.
> On top of my head I can't think of a built-in solution in R at this point
> (even though it could be argued that R might install a handler itself when
> the limit is set ...).
Yes, I think this would greatly enhanc
Jeroen,
On May 16, 2013, at 2:12 PM, Jeroen Ooms wrote:
> I would like to use setTimeLimit to abort operations that are stuck
> waiting (idle) after n seconds. Below a toy example in which Sys.sleep
> is a placeholder call that is idle:
>
> testlimit <- function(){
> setTimeLimit(elapsed=3, tra
I would like to use setTimeLimit to abort operations that are stuck
waiting (idle) after n seconds. Below a toy example in which Sys.sleep
is a placeholder call that is idle:
testlimit <- function(){
setTimeLimit(elapsed=3, transient=TRUE);
Sys.sleep(10);
}
system.time(testlimit());
However t
On 16/05/2013 9:06 AM, McGehee, Robert wrote:
Duncan, Thank you for the clarification on how delayedAssign works. Should
R-level interfaces to promise objects ever become available, I expect they
would at time come in handy.
On the subject of substitute and delayedAssign, I do have a follow-up
Duncan, Thank you for the clarification on how delayedAssign works. Should
R-level interfaces to promise objects ever become available, I expect they
would at time come in handy.
On the subject of substitute and delayedAssign, I do have a follow-up question
for the list. I'm trying to convert a
Dear all,
Do anybody know whether tools have been developed to help writing suitable
documentation for ReferenceClasses ?
Given that in the ReferenceClasses is now possible to insert the documentation
inside the method, I am wondering whether anybody have developed something
similar to javadoc
Thanks. Yes, that certainly looks like a copy/paste error when the gram* files
was moved to tools. (I just wonder why we're not using $< $@ in these rules.)
It should be harmless until someone tries actually modifying the grammar. (To
avoid relying on yacc/bison, we ship the gram*.c along with
On 13-05-16 5:26 AM, Ingo Korb wrote:
Hi!
The attached patch changes the rule that describes the actions for
gramLatex.c in src/library/tools/src/Makefile.in so it actually
generates that file instead of "gramLatex." (no extension). The
file name without extension is not referenced anywhere else
Hi!
The attached patch changes the rule that describes the actions for
gramLatex.c in src/library/tools/src/Makefile.in so it actually
generates that file instead of "gramLatex." (no extension). The
file name without extension is not referenced anywhere else and
in R-2.12 the same rule still used
10 matches
Mail list logo
