search for: findlocalized

Hi, this post is about foreach operators, the compiler package and the last update of doMC that includes support for the compiler functionality. I am using a home-made %dopar%-like operator that adds some custom expression to be executed before the foreach loop expression itself (see sample code below). It used to work perfectly with doMC 1.2.1, but with the introduction of the compiler

...and send me the results? It will display four messageboxes with a short word in the caption and a longer one in the box body. The zip file contains a compiled version of the program Thanks, Alexander N. S?rnes -------------- next part -------------- A non-text attachment was scrubbed... Name: FindLocalized.c Type: application/x-executable Size: 498 bytes Desc: not available Url : http://www.winehq.org/pipermail/wine-users/attachments/20080106/e56b56f7/attachment-0002.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: FindLocalized.zip Type: application/x-zip Size...

Thank you very much Steve. Your suggestion works perfectly -- at least with doSEQ, doMC and doMPI. Bests, Renaud On 28/06/2011 15:35, Stephen Weston wrote: > I think that the result of the concatenation should be a call object, > rather than an expression object. How about something along the > lines of: > > '%dopar2%'<- function(obj, ex) { > ex<-

Dear R fellows, Assume I define a <- expression(fn+tp) sen <- expression(tp/a) Now I'd like to know, which variables are necessary for calculating sen all.vars(sen) This results in a vector c(tp,a). But I'd like all.vars to evaluate the sen-object down to the ground level, which would result in a vector c(tp,fn) (because a was defined as fn+tp). In other words, I'd like

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability

Hello Sean and Tobias, Sean, Thank you. Could you describe Nick's ideas in few words or give me links to your discussion, so I could adapt my ideas to it. Tobias, Your patch fails on several modules in my benchmark (73 of ~1800 tests). I have sent one as attachment. See statistics files for more details, all the .ll files you could simply find in test-suite object directory (after