search for: surprises

...the criteria to be used in mapping super- to sub-sets: it's slightly stronger than "least surprise": it's "most restrictive of the two" (hey, these are professional paranoids, you know!) In the ACL space, the commensurable functions can be designed to meet "no surprises" and "more restrictive", and the others to minimize surprise in the general case, with a good chance of the result being useful to the community. My reading of map_unix_perms (nttrans.c) is that's what Jeremy is doing. --dave -- David Collier-Brown, | Always do right. Thi...

This surprised me: > reps <- 100 > sims <- list(length=reps) > sims $length [1] 100 > for(i in seq(along=sims))print(i) [1] 1 > This is R 2.8.1. Kjetil [[alternative HTML version deleted]]

When compile the following case and look at the SCEV analysis, I notice that the first two loops don't have a LoopInvariantBackedgeTakenCount (surprising) and the last one does (not surprising, except in the context of the first two examples). *void p4(int *A, int *B, long int n) {* * for (char i = 0; i < n; i++) {* * A[i + 2] = i;* * *B++ = A[i];* * }* *}* * * *void p5(int *A, int

On Tue, Jun 19, 2012 at 10:21 PM, Preston Briggs <preston.briggs at gmail.com> wrote: > When compile the following case and look at the SCEV analysis, I notice that > the first two loops don't have a LoopInvariantBackedgeTakenCount > (surprising) and the last one does (not surprising, except in the context of > the first two examples). > > void p4(int *A, int *B, long

On Wed, Jun 17, 2015 at 12:45 PM, William Dunlap <wdunlap at tibco.com> wrote: >> ... adding the ability to concat >> strings with '+' would be a relatively simple addition (no pun intended) > to >> the code base I believe. With a lot of other languages supporting this > kind >> of concatenation, this is what surprised me most when first learning R. >

...ort, just to find out that things break > > when used on s390. > > > > The documentation for virtio_config_ops now contains a comment > > explaining this, but it makes sense to add a might_sleep() annotation > > to various wrapper functions in the virtio core to avoid surprises > > later. > > > > Note that annotations are NOT added to two classes of calls: > > - direct calls from device drivers (all current callers should be > > fine, however) > > - calls which clearly won't be made from atomic context (such as > > those...

...ort, just to find out that things break > > when used on s390. > > > > The documentation for virtio_config_ops now contains a comment > > explaining this, but it makes sense to add a might_sleep() annotation > > to various wrapper functions in the virtio core to avoid surprises > > later. > > > > Note that annotations are NOT added to two classes of calls: > > - direct calls from device drivers (all current callers should be > > fine, however) > > - calls which clearly won't be made from atomic context (such as > > those...

I have to say that I was more that a bit surprised, if not to say dismayed when I booted a system with CentOS 5 installed to test a kickstart CD in interactive mode, took it to the custom partitioning screen, then rebooted without saving anything only to come up with a grub prompt, and the disk's partition table wiped. The ks.cfg file did say to wipe the disk when installing, but I would

On Wed, 20 Jun 2012 02:18:49 -0700 Eli Friedman <eli.friedman at gmail.com> wrote: > On Tue, Jun 19, 2012 at 10:21 PM, Preston Briggs > <preston.briggs at gmail.com> wrote: > > When compile the following case and look at the SCEV analysis, I > > notice that the first two loops don't have a > > LoopInvariantBackedgeTakenCount (surprising) and the last one

...(Lazy JIT ain't thread-safe), I changed the default JIT from lazy to > non-lazy. It has since come to my attention that this may have been > the wrong change, so I wanted to ask you guys. > > A couple reasons to make the default non-lazy compilation: > * The lack of thread-safety surprises new users > * Crashes due to this will be rare and so hard to track down > * The current lazy scheme is almost never the right answer for performance > * It's only one line of code to turn on lazy compilation when it is > the right answer for you. > > And a couple to default t...

I bought a very cheap server yesterday - an HP ProLiant micro server for 160 euro (280 euro with 120 cashback, for some reason). But I was surprised when I opened the box to find it didn't come with keyboard or mouse, and doesn't have the old keyboard/mouse sockets, but requires USB versions. Is that the norm nowadays? Is it possible to convert the old keyboard/mouse plugs? Also there is

On Nov 19, 2009, at 10:25 AM, Jon Harrop wrote: > > >> In this case, the assertion that LLVM is slow is correct: it's >> definitely slower than a non-optimizing compiler. > > I'm *very* surprised by this and will test it myself... Compared to a compiler in the same category as PCC, whose pinnacle of optimization is doing register allocation? I'm not

Hello everybody My collegue and I noticed a strange behaviour of R on different platforms. It's a simple computation, but results are rather different. On Windows XP: > floor(log(8,2)) [1] 3 which is what one should expect. Here's instead the result with Mac OS X (same version, 2.5.0 (2007-04-23)) > floor(log(8,2)) [1] 2 Is it a "bug" in R or in the operating

...hread-safe), I changed the default JIT from lazy to >> non-lazy. It has since come to my attention that this may have been >> the wrong change, so I wanted to ask you guys. >> >> A couple reasons to make the default non-lazy compilation: >> * The lack of thread-safety surprises new users >> * Crashes due to this will be rare and so hard to track down >> * The current lazy scheme is almost never the right answer for performance >> * It's only one line of code to turn on lazy compilation when it is >> the right answer for you. >> >>...

On Sat, Jul 23, 2011 at 5:09 PM, Talin <viridia at gmail.com> wrote: > So this was working fine for me until a few days ago when I checked out the > most recent LLVM - the one with the new type system. Now I am getting the > same error that I was getting previously. > Is it possible that your fix got unfixed when they merged in the new branch? I wouldn't be surprised if

Or just go Quantian and be happy: It has R and most of CRAN and BioC packages included. http://dirk.eddelbuettel.com/quantian.html Andy From: Brett Magill > > Better yet, forget reading the SUSE manual. For a user at your level > who wants to begin with Linux, but also wants a system that > "just works" > use Ubuntu. It is Debian based with the convenient apt-get

...non-environment object works as I would expect within the package (i.e. the attributes remain). I've looked through the documentation for reasons for this, and the only thing I've found is the mention in the language definition that "assigning attributes to an environment can lead to surprises". I'm not sure if this is one of the surprises that the author(s) had in mind! Could someone tell me whether this is expected, please? All the best, Jon -- Jonathan D Clayden, PhD Lecturer in Neuroimaging and Biophysics Radiology and Physics Unit UCL Institute of Child Health 30 Guilford...

I have started with using R on Windows, and I am really happy about the system. Now, one of my other ambitions is to learn how to use Linux, so yesterday I downloaded OpenSuse and installed that. The next problem was to try to use R with Linux. And there I met the wall. I've understood that RPM's are somewhat like installing programs on Windows, so that was downloaded and started

...t things break > > > when used on s390. > > > > > > The documentation for virtio_config_ops now contains a comment > > > explaining this, but it makes sense to add a might_sleep() annotation > > > to various wrapper functions in the virtio core to avoid surprises > > > later. > > > > > > Note that annotations are NOT added to two classes of calls: > > > - direct calls from device drivers (all current callers should be > > > fine, however) > > > - calls which clearly won't be made from atomic conte...

Dear R user community I wanted to use "bgroup" for plotting a math formula with a big "{" on the left, and nothing on the right. i used text( 10, 10, pos=4, cex=1.8, expression(F(x) == bgroup("{", x, "")), ...) on a 40 x 20 plot. surprisingly, bgroup sets "Phi(xi) = { xi" i.e. replaces alphabetic characters with greek letters in the entire