search for: 3yrs

...e -2)) { for(y in (x+1):(size -1)) { xy <- m[x,y] for(z in (y+1):size ) { xz <- m[x,z] yz <- m[y,z] # do something with xy, xz, yz } } } } I'd like to speed this up since when size gets > a few thousand, I estimate it would take 3yrs to complete the "do something" task. I could implement the "do something" in C and have it called from within the nested for loops in R, but I think I should get better performance if I implement the for loops in C as well. As such, I'm trying to get my head around looping t...

We''re experiencing a fault with our online basket, previously has worked fine (3yrs) now it sends checkout to wrong address, but only sometimes? Anyone had any experience of this? Thanks -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+...

Thanks. I was worried about the assembler invocation but it looks like you solved that problem. Smooth build on my pbook (G4, 10.2.8, gcc-3.3, ac-2.59, am-1.6.3). Only problem was lack of check for docbook-to-man; my patch is attachments 1-2. Not so smooth on my imac (G3, 10.2.8, gcc-3.3, ac-2.52, am-1.6.1; that's what came with the last 10.2-compatible dev tools). First problem: typo in

After having read this mailing list for a little while, I get the impression that there are at least some people who regularly experience on-disk corruption that ZFS should be able to report and handle. I?ve been running a raidz1 on three 1TB consumer disks for approx. 2 years now (about 90% full), and I scrub the pool every 3-4 weeks and have never had a single error. From the oft-quoted 10^14