search for: surprise

...y 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 that she can't > execute a file because one of the DOS bits was flipped on by a Windows user? Methinks "least surprise" is really only applicable to things which are very close in behavior. The is a principle of "no surprise" applicable t...

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

...unlap 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. > > 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 m...

...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...

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

>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 current behavior, where...

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 no CD drive. But there are extensive instructio...

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 surprised at all. --Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipe...

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

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 dangerous because people are using it in new and different ways. > > I would...

...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 something broke, but I would be surprised if it's exactly the same issue. It's crashing calling DIBuilder::createPointerType again? -Eli

...I met the > >> wall. I've understood that RPM's are somewhat like installing > >> programs on Windows, so that was downloaded and started with YAST. > >> > >> And got some error messages about missing stuff. The > first reactions > >> is surprise -- there must be an error in the installation > procedure. > >> I have never (well, almost) met an installation procedure > on Windows > >> that did not include everything needed. And the > installation of R on > >> Windows was very smooth. Then I discove...

...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 Guilfor...

...talled 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 with YAST. And got some error messages about missing stuff. The first reactions is surprise -- there must be an error in the installation procedure. I have never (well, almost) met an installation procedure on Windows that did not include everything needed. And the installation of R on Windows was very smooth. Then I discover to my big surprise that the readme file says that I need...

...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 cont...

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