I skimmed some of their c api and it looked pretty usable.
On Fri, Sep 18, 2015 at 9:02 AM -0700, "Keno Fischer" <[email protected]> wrote: Arrayfire is written in C++, so the C++ is by far the simplest way to interface with it. This work was mostly exploratory, to see if it was useful at all. If somebody wanted to seriously use it now, I could see wanting to rewrite it using the C interface, but that would be a simple task once the API is figured out. Alternatively, just wait until the C++ interface is considered sufficiently mature. On Fri, Sep 18, 2015 at 7:28 AM, Viral Shah <[email protected]> wrote: > I believe the C interface is not as well supported as the C++ one, but I > could be wrong. That is probably why Keno chose the C++ interface. He could > perhaps say more. > > -viral > > > > > On 18-Sep-2015, at 3:37 pm, Tim Holy <[email protected]> wrote: > > > > I don't know anything about ArrayFire, but this seems potentially > interesting. > > > > Checking the code, it seems like you used the Cpp interface rather than > what > > appears to be an available C interface. Any particular reason? (As in, > "don't > > use the C interface, it doesn't work"?) > > > > --Tim > > > > On Friday, September 18, 2015 01:14:25 AM Viral Shah wrote: > >> We at Julia Computing have done some exploratory work on ArrayFire.jl, > >> which is now available here. This is not a supported package at the > moment, > >> but that could change in the future. For now, we are putting out what we > >> have done. > >> > >> https://github.com/JuliaComputing/ArrayFire.jl > >> > >> -viral > >> > >> On Tuesday, November 18, 2014 at 10:17:45 AM UTC+5:30, Zahirul ALAM > wrote: > >>> I second this. > >>> > >>> On Monday, 17 November 2014 12:27:43 UTC-5, Test This wrote: > >>>> Happy to see thus reaction from a core julia developer. Hope julia > makes > >>>> parallel programming on CPUs and GPUs easier. > > > >
