search for: surprising

[This is fairly far from the topic of the mailing-list: we may want to take further discussion to email or the tech list] Jeremy writes: > it violates the principle of > least suprises for the nfs user. ie. They may get access > denied when the UNIX perms say they should be granted access. Paul replies: > But wouldn't it also be a "surprise" when an NFS user finds

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 *B, long int n) {* * for (short i = 0; i < n; i++) {...

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 int n) { >   for (char i = 0; i < n; i++) { >     A[i + 2] = i; >     *B++ = A[i]; >   } > } > > void p5(int *A, int *B, long int n) { >  ...

...>> 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. > > Wow! R has a lot of surprising features and I would have thought > this would be quite a way down the list. Well, it is hard to guess what users and people in general find surprising. As '+' is used for string concatenation in essentially all major scripting (and many other) languages, personally I am not surprised t...

...ort is free to implement some of the callbacks in > > virtio_config_ops in a matter that they cannot be called from > > atomic context (e.g. virtio-ccw, which maps a lot of the callbacks > > to channel I/O, which is an inherently asynchronous mechanism). > > This can be very surprising for developers using the much more > > common virtio-pci transport, 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() annotati...

...ort is free to implement some of the callbacks in > > virtio_config_ops in a matter that they cannot be called from > > atomic context (e.g. virtio-ccw, which maps a lot of the callbacks > > to channel I/O, which is an inherently asynchronous mechanism). > > This can be very surprising for developers using the much more > > common virtio-pci transport, 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() annotati...

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

...mail.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 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]; > >   } > > } > > >...

>From where I sit, this boils down to a very simple question (modulo Chris's point): Either choice will surprise some users. Which surprise is worse? Personally, I'd always prefer correct but slow behavior by default, and explicitly enabling dangerous (but in some cases fast) behavior. I would also point out that it seems that most of the people new to the JIT are surprised by the

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

...sults 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 system? Anyway, it's quite a surprising one. _____________________________________ Fausto Galli Institute of Finance University of Lugano Via G. Buffi 13 CH-6904 Lugano, Switzerland. +41 (0)58 666 4497 http://www.people.lu.unisi.ch/gallif

On Oct 28, 2009, at 10:07 AM, Chandler Carruth wrote: > From where I sit, this boils down to a very simple question (modulo > Chris's point): Either choice will surprise some users. Which surprise > is worse? Personally, I'd always prefer correct but slow behavior by > default, and explicitly enabling dangerous (but in some cases fast) > behavior. The behavior is only

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

Dear all, I am trying to create an environment object with additional attributes, viz. Foo <- structure(new.env(), name="Foo") Doing this in a standard session works fine: I get the environment with attr(,"name") set as expected. But if the same code appears inside a package source file, I get just the plain environment with no attributes set. Using a non-environment

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

...ment some of the callbacks in > > > virtio_config_ops in a matter that they cannot be called from > > > atomic context (e.g. virtio-ccw, which maps a lot of the callbacks > > > to channel I/O, which is an inherently asynchronous mechanism). > > > This can be very surprising for developers using the much more > > > common virtio-pci transport, 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...

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 formula. I tried out other ending delimiters instead of "": With " ", ":", ";", ",", R complains about an "invalid group delimiter&...