similar to: Assigning to a vector while keeping the attributes

Hello Richard As discussed in the IRC channel, when merging a moderately large reg file (~35MB) to a hiv file (~118 MB); hivex generates a huge hiv file (~580 MB). These changes address that by creating a list of unallocated blocks and reassigning unused blocks. I used https://github.com/msuhanov/regf/blob/master/Windows%20registry%20file%20format%20specification.md as a reference for the

Hi, We've encountered a difference in running time between a straight function call and the same call using do.call when the called function generated an error. We've isolated the problem to the following small reproducible example: Consider the following function: foo <- function(nr = 2e6, nc=3, use.do.call = FALSE) { nn <- paste("V", 1:nc, sep="") z <-

Hi Fresh 4.2 install on a box that has the following RAID card GDT-HA: Storage RAID Controller Driver. Version: 3.04 ACPI: PCI interrupt 0000:03:09.0[A] -> GSI 27 (level, low) -> IRQ 225 GDT-HA: Found 1 PCI Storage RAID Controllers Configuring GDT-PCI HA at 3/9 IRQ 225 GDT-HA 0: Name: SRCU31L scsi2 : SRCU31L Vendor: Intel Model: Host Drive #00 Rev: Type: Direct-Access

Hi, Trying to decrease the size of a SEXP variable without reassigning values individually in a loop. So far, I've tried using Realloc, as the follow source demonstrates: SEXP dothis() { SEXP Rblah; PROTECT(Rblah = NEW_INTEGER(6)); int* blah = INTEGER(Rblah); blah[0] = 1; blah[1] = 2; blah[2] = 3; Realloc(Rblah, 3, INTEGER); UNPROTECT(1); return(Rblah); } According to the

On Mon, Jul 23, 2018 at 02:38:18PM -0400, Shreyas Khare wrote: > Hello Richard > > As discussed in the IRC channel, when merging a moderately large reg > file (~35MB) to a hiv file (~118 MB); hivex generates a huge hiv > file (~580 MB). These changes address that by creating a list of > unallocated blocks and reassigning unused blocks. I used

Hi, I seem to not be able to assign NULL to an element of a pairlist without causing it to be coerced to a plain list. For example: > x <- pairlist(1, 2) > class(x) [1] "pairlist" > x[1] <- list(NULL) > class(x) [1] "list" This actually true for all [()<- assignments regardless of list value, e.g. > x <- pairlist(1, 2) > x[1] <- list(0) [1]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, in May 2015 I reported [0] that I can not import my S/MIME certificate. Issuer is GlobalSign. Jan Horak reassigned it to the nss guys ("This seems to be problem in NSS code, reassigning to nss component"), but then the ticket idled and was eventually closed by EOL of Fedora 21 (though I stated it persists with F22). I just reopened

Hi. I want to play the old '97 game "Claw". It installs and runs, but strangly I can't jump in it! No matter what I use, keyboard or gamepad. Normally, if you tap the spacebar, the character makes a low jump; if you hold the spacebar, he makes a high jump. However, under wine all jumps are low. Other movements work fine though. I even tried to run the game under winxp guest in

Hi, in my packages/functions/code I tend to remove large temporary variables as soon as possible, e.g. large intermediate vectors used in iterations. I sometimes also have the habit of doing this to make it explicit in the source code when a temporary object is no longer needed. However, I did notice that this can add a noticeable overhead when the rest of the iteration step does not take that

Hi, I have a question about llvm/ADT/DenseMap.h and llvm/IR/ValueMap.h: When you have a: MapType M; is it safe to do: M[NewKey] = M[OldKey]; or do you need to do it in two steps: auto tmp = M[OldKey]; // ensure the reference to M[OldKey] is copied, before reassigning. M[NewKey] = tmp; // might reallocate aka, will a possible allocation for M[NewKey] invalidate the

Dear all I am trying to find the best way to handle large fields in reference classes. As the code below shows assignment via <<- causes many copies to be made if the subsetting is extensive (in modb1). This can cause R to run out of memory. Creating a local copy and using the optimisation in <- is the best solution I have found so far (in modb2) - but it is not really much better than

reassign 768005 src:xen 4.11.1-1 thanks Hi, I was browsing the bash-completion package bug list before filing a bug to remove the obsolete 'xm' file, and then I ran into this one. Reassigning to Debian Xen team, since I that makes more sense. We totally missed this on our (release) radar. And indeed, we're shipping the upstream completion file now. Adi, I see how you're

Hi Henrik, It would help to understand your use case for pairlists. Thanks, Michael On Wed, Oct 12, 2016 at 9:40 AM, Michael Lawrence <michafla at gene.com> wrote: > The coercion is probably the most viable workaround for now, as it's > consistent with what happens internally for calls. All pairlists/calls > are converted to list for subassignment, but only calls are

Hi. I'm trying to find a systematic way to prevent assignment to names of existing functions. I've tried reassigning to the assignment operator, with mixed results. The function definition for "<-" below works as hoped for the demonstrated assignments to a and c. However, for the assignment based on the test function, it appears that the formal argument is not

Hello, I am currently trying to translate some custom IR to LLVM-IR and came across and issue. The custom IR has several registers and I am basically try to SSAfy it so it can be easily translated/converted to LLVM-IR. The problem: Since in my custom IR I can reassign every register I have to reassign every new expression with a new llvm Value. But my IR has something like this: REG A = VAR C

I want to keep the translation short and simple (My IR doesn't have control flow so it's basically on basic block) that's why I don't want to rely on alloca/load/store. 2016-02-08 6:08 GMT+01:00 George Burgess IV <george.burgess.iv at gmail.com>: > Hi! > > I don't know what "the right way" to do this is, but is there any reason > you're against

All, I'm working on a script to automatically assign uidNumber and gidNumber attributes to users. I have a few questions: 1) Which users should be excluded from this assignment? I'm currently using this LDAP filter (simplified syntax used here): (objectClass=user) & (objectCategory=Person) & ~(sAMAccountName=krbtgt*) Specifically, based on recent conversations, I'm

Okay, someone explain this behaviour to me: Browse[1]> replace(rep(0, 4000), temp1[12] , temp2[12])[3925] [1] 0.4462404 Browse[1]> temp1[12] [1] 3926 Browse[1]> temp2[12] [1] 0.4462404 Browse[1]> replace(rep(0, 4000), 3926 , temp2[12])[3925] [1] 0 For some reason, R seems to shift indices along when doing this replacement. Has anyone encountered this bug before? It seems to crop up

Thanks, this was what I expected. There is a desire to eliminate the usage of pairlist from user code, which suggests the alternative of allowing for function arguments to be stored in lists. That's a much deeper change though. On Wed, Oct 12, 2016 at 12:31 PM, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote: > Michael, thanks for this info. > > I've stumbled upon

Assigning one or more values to a vector/matrix/array x for which length(x) == 0 gives no error, e.g. > x <- integer(0) > x[] <- 1:2 > x <- matrix(nrow=0, ncol=1) > x[] <- 1:2 > x[,1] <- 1:2 > x <- array(dim=c(0,1,1)) > x[] <- 1:2 > x[,1,1] <- 1:2 whereas > x <- integer(1) > x[] <- 1:2 Warning message: In x[] <- 1:2 : number of