search for: nfinished

After a year my R programming style is still very "C like". I am still writing a lot of "for loops" and finding it difficult to recognize where, in place of loops, I could just do the same with one line of code, using "sapply", "lapply", or the like. On-line examples for such high level function do not help me. Even if, sooner or later, I am getting my R

...see it? That's weird... root at alfa:~# strace -vffF /etc/init.d/dovecot start 1>& ~/dovecot.strace root at alfa:~# less ~/dovecot.strace [...] :/chroot [...] :/dovecot-pgsql.conf [pid 18211] open("/var/log/dovecot_info.log", O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE, 0666 <u nfinished ...> [pid 18213] fcntl64(5, F_SETFD, FD_CLOEXEC <unfinished ...> [pid 18211] <... open resumed> ) = 5 [pid 18213] <... fcntl64 resumed> ) = 0 [pid 18211] fstat64(5, <unfinished ...> [pid 18209] <... fcntl64 resumed> ) = 0 [pid 18211] <... fstat64...

Hi, I am new in R and have some frustrations as how to set debug breaks during emacs R debug. I use debug () as where or which function to debug. But during the debug, e.g., I have a for loop at the beginning of the function code and want the code execution to jump through that for loop and set a break after that. How to do that? Is there a web site detailing the syntax of the debugging of R?

...ptr=&ptrs[1]; for (i=0;i<nx;i++) { REAL(lon)[i] = *(ptr+i); } ptr=&ptrs[2]; for (j=0;j<ny;j++) { REAL(lat)[j] = *(ptr+j); } ptr=&ptrs[3]; for (k=0;k<nt;k++) { REAL(tim)[k] = *(ptr+k); } ptr=&ptrs[4]; REAL(missing)[1]=*ptr; printf("\nFinished successfully!\n"); /* Garbage collecting */ UNPROTECT(7); return(field); } -- ______________________________________________________________________________ Rasmus E. Benestad, D.Phil, GradInstP, The Norwegian Meteorological Institute rasmus.benestad at dnmi.no http://ho...