search for: portable_

...1148.16 5-Apr-04,1141.81,1150.57,1141.63,1150.57,1614749952,1150.57 2-Apr-04,1144.15,1144.73,1132.17,1141.81,2134489984,1141.81 1-Apr-04,1128.14,1135.53,1126.21,1132.17,1765560064,1132.17 <!-- chart2.finance.scd.yahoo.com uncompressed Sat Apr 24 15:27:40 PDT 2004 --> Is there an _elegant and portable_ way of reading this with the last line? I needed this, and used the somewhat clunky data <- read.csv(destfile) unlink(destfile) data <- data[-(nlines-1),] # skip very last line with commment which uses nlines, which had already been computed (as has a offset of one bec...

...manipulate the LLVM infrastructure via ctypes as a shared object / dll -- no C required! Those of us interested in talking to LLVM from Lisps, either Common Lisp (via CFFI) or a scheme like PLT/Mzscheme, can also use the shared library interface. In fact, for the Common Lisp case, this is the _only portable_ (cross-implementation) way of talking to LLVM. If anyone's interested in Here is a one-off example of python using the shared library approach and Gordon's excellent C interface (llvm-c): http://pastebin.com/m5197c5e7 (the verbosity at the beginning is because of some linkage issue...

If SWIG can be made to do a good job with Python/Ruby/Perl etc bindings around LLVM, I would be very interested in this. I'm personally interested in seeing both Python and Ruby bindings, and in having them be as easily maintained as possible. I think it would be interesting to see what the SWIG-style solution can do in this direction as opposed to the C-binding approach. If it results in

Hi, I've been lurking around the LLVM project for a couple of months now. The two recent threads about python bindings for LLVM ([1] and [2]), combined with the fact that I am looking for at GSoC project at the moment. Lead to the idea of making the "public" parts of LLVM SWIG[3]-friendly and basing a set of python bindings on this. My reasoning for doing it this way, is that it