search for: contorted

Hello, I need to take a dot product of each row of a dataframe and a vector. The number of columns will be dynamic. The way I've been doing it so far is contorted. Is there a better way? dotproduct <- function(dataf, v2) { apply(t(t(as.matrix(a)) * v2),1,sum) #contorted! } df = data.frame(a=c(1,2,3),b=c(4,5,6)) vec = c(4,5) dotproduct(df, vec) thanks, allie

At 19:49 07/09/00 -0700, A.J. Rossini wrote: > >I've had some "interesting" emails with Frank a while back (years?) >over this. He's got some valid points, and some amusing points... > >He's also recently realized the extent and importance that licenses >have in the real world. > >However, the port is fairly major (I know a few people who will

Hi there I would like to setup my puppetmasterd behind my ADSL modem and manage the nodes on the hosting sites. I can imagine opening ports to the puppetmasterd server will work. Am I right? On the other hand an ideal configuration for me would be a Reverse Proxy setup, so I don''t have to touch the ADSL router. Has anyone setup a puppetmasterd behind a reverse proxy? Any pointers,

Thanks for the detailed response! :-) > This is by design. LLVM's type system is very low-level... Yes, and it should remain low-level. :-) > Expecting it to directly support generics seems a third-order-of- > magnitude leap of faith. :) But there is good news for the faithful? Let us distinguish between generics as found in java or .Net, and parametric polymorphism in general.

Hi Folks, I need some large chunk of physical memory, so I allocate it early using alloc_bootmem_low_pages and use it later (akin to bigphysarea patch). The trouble I am having is the following. Suppose the virtual address for the memory area is 0xc14d6000. After xen_create_contiguous_region call, I do a virt_to_bus and the bus address comes out to be 0x18000000. So far so good. However,

...uys are really overthinking this: volatile should be volatile should be volatile. It makes the behavior of volatile easy to understand, it makes it easy to use, it allows LLVM to support the rules for the volatile keyword in C (AFAIK), and it doesn't require you to guess all the different, contorted ways in which volatile could be used. -- John T. > Ciao, > > Duncan. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Affected Software: rssh - all versions prior to 2.3.0 Vulnerability: local user privilege escalation Severity: *CRITICAL* Impact: local users can gain root access Solution: Please upgrade to v2.3.1 Summary ------- rssh is a restricted shell which allows a system administrator to limit users' access to a system via SSH to scp, sftp, rsync, rdist, and cvs. It also allows the system

Hi Torok, >>> Well...strictly as LLVM IR I find externally visible incorrect >>> behavior unlikely, it's just a "different definition". For C and >>> C++, I'd be looking at more complicated variations of >>> >>> int main() >>> { >>> volatile int i = 1; >>> return 0; >>> } >>>

On 2009-02-18, at 14:53, DeLesley Hutchins wrote: > On 2009-02-18, at 08:06, Gordon Henriksen wrote: > >> Still, there are a large number of potential foibles here. For >> instance, passing an argument can require platform-specific >> contortions to conform to the platform ABI... > > Are those contortions done by the native code generator back-end, or > are

Hi, I'm in the position that a network console would occasionally be very useful for me to control pxelinux. Has the possibility of adding it (next to VGA and serial) been ever discussed? I understand that it may sound somewhat contorted, but it could also serve instead of a TFTP PUT for extracting hardware info, for example... How hard would it be to add (considering gPXE as well)? -- Cheers, Feri.

Hi All, I've been trying to put together a one off CentOS 4 based distro, and I ran into some trouble. First off just so you know we've been doing this with CentOS 3 and with RedHat 9 before that, so the inexperience is only with the delta between CentOS 3 and CentOS 4 (and RHEL 3 and RHEL 4 by extension). Anyway, the problem is that for some reason /dev/console is not getting created.

...ng system, so it would seem odd to have to temporarily install >> llvm-gcc to build llvm, but then install llvm-gcc in a separate package. >> > > That issue goes away with llvm-gcc4. You would simply build llvm and > then build llvm-gcc4. With llvm-gcc3, its a little more contorted: > > 1. build llvm tools only (don't build the runtime) > 2. build llvm-gcc3 > 3. build the llvm runtime library > Hi Reid, I got llvm all up and running, thanks. I'm now trying to set up llvm-gcc4. Does llvm-gcc4 require the llvm object files, or can I install llvm, r...

On Fri, 17 Aug 2007, David Greene wrote: > Ah. Basically operator<< for FILE*. I don't see a lot of benefit to > redefining operator<< for every type just to avoid ostreams. The > problem isn't basic_ostream _per_se_. There are two issues we're > worried about: The problem is basic_ostream and the design of the whole iostreams library. Use of virtual base

I have a Gentoo linux (OpenRC) desktop connected to a UPS, the brand is Vultech, but lsusb gives me this: Bus 003 Device 006: ID 0925:1234 Lakeview Research and I found an article about this hardware here, someone had it working with the richcomm_usb driver: http://verahill.blogspot.it/2012/12/kstar-australia-1500-va-ups-on-debian.html So, I installed nut and configured my UPS to work with the

On Friday 17 August 2007 13:17, Chris Lattner wrote: > On Fri, 17 Aug 2007, David Greene wrote: > >> Posix is pretty available, what system doesn't have them? > > > > Windows, for one. If POSIX is ok, it's better in my mind to just > > directly > > Windows has POSIX calls. Ok, I'll admit I don't know a lot about what's available there.

I found that predict.gnls failed with a wierd error message about a non-numeric argument to a binary vector in one of three nearly identical uses. Error in Inh/Ki : non-numeric argument to binary operator (Inh and Ki are arguments to the function used in the formula for the object whose predictions were requested). It turns out that the problem is in getCovariateFormula(). The final line in

...is a source-based > packaging system, so it would seem odd to have to temporarily install > llvm-gcc to build llvm, but then install llvm-gcc in a separate package. That issue goes away with llvm-gcc4. You would simply build llvm and then build llvm-gcc4. With llvm-gcc3, its a little more contorted: 1. build llvm tools only (don't build the runtime) 2. build llvm-gcc3 3. build the llvm runtime library > > Thanks for all your help! You're welcome. Reid. > > -e > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiu...

On Fri, 17 Aug 2007, David Greene wrote: >> Posix is pretty available, what system doesn't have them? > > Windows, for one. If POSIX is ok, it's better in my mind to just directly Windows has POSIX calls. > use open, write and friends, which is what I do now. Going the cstdio > route should only be done for portability reasons to support non-POSIX > systems. I

Rails has many built in validation methods to ensure that an ActiveRecord instance cannot be created or updated under certain situations (typically caused by invalid data). However, I can find no methods to govern whether an ActiveRecord instance can be destroyed. Essentially, I wish an error to be raised when a user tries to delete an ActiveRecord without first adhering to a certain set of

On Friday 17 August 2007 17:01, Chris Lattner wrote: > On Fri, 17 Aug 2007, David Greene wrote: > > Ah. Basically operator<< for FILE*. I don't see a lot of benefit to > > redefining operator<< for every type just to avoid ostreams. The > > problem isn't basic_ostream _per_se_. There are two issues we're > > worried about: > > The