search for: protability

hi all, is there a cd-rom image with a full R pre-installation which I can give to my students so that if they want to run R on their computer, they will be able to run it from the cd-rom without having to install it on their computer. That way, they can have a 'protable' R package installation in their bags, and they can use it on any machine. Is this possible? Dr. Iasonas Lamprianou

Hi, I want to implement Ogg Vorbis support for the Lyra2 protable player but need help. Thompson ======== I would like to get additionnal information on the tools (and agreements) needed to develop support code for additionnal file formats for the Lyra2, such as Ogg Vorbis. Thompson is big, please forward my request to adequate department. <p>(Not so ) Technical Info

I just read some of the discussion on the list about 'bitrate peeling' and remembered an interview of Monty that I have read recently. In it he says that Vorbis uses MCDTs <sp> and that these are theoretically reversable. And now, I learn that theoretically we can use bitrate peeling to make smaller files from larger ones, and that leads to my question. Could I theoretically

...t;. Yes, making sure it serves as a good example of using the API is a good idea. Not sure all tests would be that, but it is a good goal. The tests I have in mind are: * --dump-module basically just llvm-dis, tests memorybuffer/bitreader already implemented in patch, uncertain about protability as it does dup2 tricks to dump to stdout * --list-module-functions tests basic iteration over stuff in module implemented in patch, want to extend it to iterate over instructions too * --list-module-globals ditto * --disassemble Test llvm-c/Disassebler.h. Not sur...

...as a good example of using the API is a > good idea. Not sure all tests would be that, but it is a good goal. > > The tests I have in mind are: > > * --dump-module > basically just llvm-dis, tests memorybuffer/bitreader > already implemented in patch, uncertain about protability as it > does dup2 tricks to dump to stdout > > * --list-module-functions > tests basic iteration over stuff in module > implemented in patch, want to extend it to iterate over > instructions too > > * --list-module-globals > ditto > > * -...

I like the idea, but I find the name confusing; I think it should have `llvm-c` or `c-api` somewhere in the name. This could also serve as a simple example of using the API. -- Sean Silva On Mon, Sep 23, 2013 at 4:00 PM, Anders Waldenborg <anders at 0x63.nu> wrote: > Moving this to llvmdev. > > On Fri, Sep 20, 2013 at 08:26:41AM +0200, Anders Waldenborg wrote: > > >

Moving this to llvmdev. On Fri, Sep 20, 2013 at 08:26:41AM +0200, Anders Waldenborg wrote: > > > This avoids warnings when included in a application that > > > uses -Wstrict-prototypes. > > > > > > > Should we enable this warning in CFLAGS for LLVM builds to catch this > > sooner? > > It is a C-only warning, and AFAICS there is no C code in

...if you keep the number of > > > > macro's limited. > > > > > > The reason XTRACE was introduced in the first place is to automatically > > > put a function name as prefix into trace output through the use of > > > __FUNCTION__. if it is (again) a protability problem, we could always > > > workaround this as follows (taken from gcc manual): > > > > > > > > > #if __STDC_VERSION__ < 199901L > > > # if __GNUC__ >= 2 > > > # define __func__ __FUNCTION__ > > > # else &g...

Hi all, I know this question has been asked in the past, but I am wondering if anyone running R on Linux has any guidance as to a text editor that works well with R. At the present time I am running R on Windows and using TINN-R. For a number of reasons I want to switch to Linux, but can't find much in the way of a text editor in sync with R. Any experiences, recommendations would be