similar to: [LLVMdev] getting and setting array indices c interface

Hello everyone, I am working with plm package and I have problem with random and within models, which are giving errors which says "empty model". However, the model is not empty. In the source code for plm.fit, where the error originates it says something like (writing from the top of my head...) X <- model.matrix(formula,data, lhs=1,...) if (ncol(X) == 0) stop("empty

Hi R gourmets, I am trying to convert an HTML table into an xts object. The table has six columns, with the data of interest in a single row with each cell containing a long, \n-delimited character string. Initially, I work with these strings as elements in a list. This is necessary because the strings in each cell do not translate into a regular matrix with equal-length columns. Once I fix

Hello, I'm trying to get to grips with the c interface of llvm intending to eventually develop a front end for Purebasic Though I've hit the wall already writing an iterative Fibonacci function. While I think the module dump looks ok it doesn't work for any input > 2 the function returns 2, the loop only executes once Hopefully someone can see what the problem is from the

Attached is what I got thus far. What I'm struggling with is proper integration in build system. What is in there is just wild guesses from my side, both on autoconf and cmake variants. It would be great if someone with proper knowledge of the buildsystems could have a look. Also I'm not sure how to properly handle compilation on msvc - clearly "-std=c11 -Wstrict-prototypes" is

I''m curious why the Parameter block check for the with is going to be removed. I like the concept of clean, readable tests, however I also like to test as efficiently as possible. For some tests, I''ll take the approach of putting test assertions inside the parameter block, and always returning true. This is a contrived example: def test_something mock =

2015-08-17 13:47 GMT-07:00 David Blaikie <dblaikie at gmail.com>: > > > >> >> I'd propose that the only 100% strict rule should be that if the ABI/API >> changes, it is done in a way that *loudly* breaks old programs -- e.g. they >> fail to compile, link, or run (depending on how the other-lang wrappers are >> accessing the API functions) -- not

> > > On the original question though, why isn't there something "off the > shelf" > > that will do what I want? Surely, a "boxplot" using mean, SD, max and > min > > would be a common enough need to justify it? > > > > Gabor Grothendieck replied: > tarr is not a list or a data frame. Use.data.frame(tarr) so that it > uses

As someone who used the LLVM C API for an experiment back in 2009ish (porting the SBCL lisp compiler to target LLVM as a backend -- never finished), I thought it was great that LLVM provided the C API. I was sad that it wasn't properly updated to include support for all the newly introduced IR features, though. (E.g. atomics). I tried to send patches for some of that stuff a while later, but

Hi all, At the dev meeting I promised to update everyone on where my work with opaque pointers is right now. It's taken me a while, but at least it's the same year! Current Status ============== I've put two branches up at https://github.com/TNorthover/llvm-project: "opaque-ptr" which has most of the real work so far; and "opaque-ptr-always" that additionally has

On Sun, Aug 16, 2015 at 10:34 PM, deadal nix via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > 2015-08-16 21:51 GMT-07:00 Eric Christopher <echristo at gmail.com>: >> >> The promise of stability. We don't promise that the C++ API will stay >> stable. >> > > > Why was that promise be made in the first place ? Has it been made in the >

The Wine development release 1.3.37 is now available. What's new in this release (see below for details): - Completion of the DIB engine. - Improvements to the C++ runtime. - A number of fixes in the audio drivers. - Unnecessary Direct3D options removed from WineCfg. - Some fixes to the built-in Internet Explorer. - Various bug fixes. The source is available from the following