search for: suprise

Is this a known bug? Suprisingly google didn't turn up much. I'm running DDR RAM and a AMD XP processor on CentOS 4.

G'day Federico, On Wed, 17 May 2023 10:42:17 +0000 "Calboli Federico (LUKE)" <federico.calboli at luke.fi> wrote: > sexsnp = rep(NA, 1750) > for(i in 1:1750){tryCatch(sexsnp[i] = fisher.test(table(data[,3], > data[,i + 38]))$p, error = function(e) print(NA))} Error: unexpected > '=' in "for(i in 1:1750){tryCatch(sexsnp[i] =" Try: R> for(i in

... or just put the R expression inside curly brackets, e.g. tryCatch({ sexsnp[i] = fisher.test(table(data[,3], data[,i+38]))$p }, error=function(e) print(NA)) Exercise: Compare > list(a = 2) $a [1] 2 with > list({ a = 2 }) [[1]] [1] 2 and > list(b = { a = 2 }) $b [1] 2 BTW, note how the latter two assigned a <- 2 to the global environment. /Henrik On Thu, May 18, 2023 at

I may be making a simple error, but I've looked at the str() of the resulting objects and I can't see any obvious reason I'm having the problem I am having, so I am reaching out to the R-help group. ?I am generating a string in my code. ?When I make a slight modification (add a comma at the end using my "lastcomma" function), I can no longer successfully write that string to

Because `<-` and `=` do different things (and I am one of the old fossils that wish they had not been confounded). `fun(x <- expr)` Assigns the value of `expr` to the variable `x` in the frame/environment that `fun` is called from. `fun(x = expr)` Assigns the value of `expr`to the variable `x` in the frame/environment created for and used by `fun` subject to the rules of argument matching.

Hi, On samba 3 winserver enabled On xp I can work with smb on 2 ways 1 ) smb over tcpip without netbios. I was suprised because I can logged onto the domain. Xp client found the primary domain controler. I am not able to add permissions ( only the local machine domain is visible ). How xp client found the DC ( cache DC name on the client , wins answer on port 445 ?) 2 ) smb over netbios. Samba works with port 139....

Hello, I run a fisher.test() in a loop, with the issue that some of the data will not be useable. To protect the loop I used tryCatch but: sexsnp = rep(NA, 1750) for(i in 1:1750){tryCatch(sexsnp[i] = fisher.test(table(data[,3], data[,i + 38]))$p, error = function(e) print(NA))} Error: unexpected '=' in "for(i in 1:1750){tryCatch(sexsnp[i] =" But this works: for(i in

hello, I'm suprised that an SRC.RPM from the rhel5 repo needs a file from FC7. I grabbed rpmdevtools from http://download.fedora.redhat.com/pub/epel/5/ it rebuilds fine as EL5, but when I go to install it, it requires a version of rpm-build higher than the C5 base version (4.4.2-37) --------------------- grab depen...

I was a bit suprised to note that demo files are not run as part of R CMD check. This seems out of keeping with the philosophy of running all code contained in the package (in the source, in examples etc). Should demo files be checked as part of R CMD check? Hadley

...ents though: 1. Morton, the pattern isel is now on by default for X86, and that option doesn't exist. If you update to CVS you can remove that. Using -enable-x86-fastcc should work with CVS though. 2. I haven't done much testing with the JIT and tail calls. I wouldn't be suprised if there are minor issues that need to be fixed. I will try to take a look and see what remains to be done over the next couple of days. -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/

...should just work if the clients (wmp, real) have support for the >metadata >- and since you say that it works if you rebroadcast via peercast, this >suggests that they _do_ have support. WMP does not support shoutcast-style metadata....definately not. And I'd be REAL (pun intended) suprised if Helix/Real supported it. <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the b...

Chris Lattner wrote: > On Wed, 18 May 2005, Chris Lattner wrote: > >> Yup, something like this should work. Two comments though: >> 2. I haven't done much testing with the JIT and tail calls. I >> wouldn't be >> suprised if there are minor issues that need to be fixed. I will try >> to take a look and see what remains to be done over the next couple of >> days. > > > As I expected, there were issues. I fixed the following two problems: > > 1. The JIT didn't know where a call ca...

...pear to exhibit the problem. It's only the native servers running on dual PIII1000+ hardware which suffer. As you can imaging, testing is a bit difficult due to it involving causing a live server to potentially need a hardware reboot which is something i'm not particularly keen on doing (suprise, suprise) In all other respects, each server functions perfectly in all other respects and certainly in respect to SMB file serving. Any hints, pointers or suggesions (unless they revolve around Win2k as an alternative file server....) will be greatfully received Alex

Hey All, I think I found a bug but I would be suprised since it would cause major problems. We setup the asset_host in init.rb with: if File.exist?(facebook_config) FACEBOOKER = YAML.load_file(facebook_config)[RAILS_ENV] ENV[''FACEBOOK_API_KEY''] = FACEBOOKER[''api_key''] ENV[''FACEBOOK_SECRET_KEY'...

Oh Boy. User 'Administrator' in your existing directory has SID S-1-5-21-2070472328-935435760-1634736958-1000, expected it to be S-1-5-21-2070472328-935435760-1634736958-500 ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: User 'Administrator' in your existing directory does not have SID ending in -500 It's not all

...> as much information as you can provide since it may not be a target that > the majority of the developers have access to. The target is OpenBSD/i386 for now and later sparc64 and amd64. Most of the errors are to do with GNU grep syntax not being compatible with BSD grep. I would not be suprised if solaris and FreeBSD were impacted by this too. The solution is to use egrep we *think*. There are a couple we are scratching our head on. One being the negative zero test. It seems the display function in llvm-dis (probably printf) is truncating the minus sign from the output deeming it poi...

..._encode. I tracked it down to a mis-calculated buffer size for malloc. I've attached the patch that fixes it (for me:). The only problem I have with the rest of the code is figuring out how the terminating 0 (null, whatever:) gets into unicode, I can't see anywhere that sets it, so I'm suprised make_utf8_string doesn't cause any problems. Bill -- Leave others their otherness. -- Aratak <HR NOSHADE> <UL> <LI>text/plain attachment: oggenc.patch </UL> -------------- next part -------------- A non-text attachment was scrubbed... Name: oggenc.patch Type: appl...

...puts the text at the correct positions, however, it has another problem. I would like to rotate the text, but if I use 'str=90' (to rotate the text for 90 degrees), I get a warning massage: Warning message: parameter "str" couldn't be set in high-level plot() function This suprises me, since if I read the help correctly ('?par'), then this should not happen. So if anyone can either hepl me to rotate the text in 'text' or to correctly plot the text in 'axis', I would be very grateful. Ales

...tion in development mode. Intermittenly we get an error on some pages, saying : undefine class/module User. If we refresh the page, the error goes away and we see the html correctly rendered. User is a model defined in the models directory and has been listed in application.rb as model :user. I am suprised by the fact that this happens only occasionally. Can someone suggest what might have gone wrong? Thanks, Yash -- Posted via http://www.ruby-forum.com/.

...en wrote: > Chris Lattner wrote: > >> On Wed, 18 May 2005, Chris Lattner wrote: >> >>> Yup, something like this should work. Two comments though: >>> 2. I haven't done much testing with the JIT and tail calls. I >>> wouldn't be >>> suprised if there are minor issues that need to be fixed. I will try >>> to take a look and see what remains to be done over the next >>> couple of >>> days. >> >> >> >> As I expected, there were issues. I fixed the following two problems: >>...