search

arrayfire / arrayfire-dotnet

.NET wrapper for ArrayFire
BSD 3-Clause "New" or "Revised" License
78 stars 21 forks source link

Discussion for creating the ArrayFire .net API #1

Closed pavanky closed 8 years ago

pavanky commented 9 years ago

@umar456 @9prady9 We do not need to do it right away, but if you guys have ideas, this would be the place to discuss.

9prady9 commented 9 years ago

We can start with C++/CLI to facilitate usage from other languages in .NET family.

royalstream commented 8 years ago

Hi,

As per the conversation I had with Pavan Yalamanchili I forked and created a draft of a wrapper and just did a PR (see https://groups.google.com/forum/#!topic/arrayfire-users/1N0qYpZFC-Q)

All the boilerplate Interop code is automatically generated from your header (*.h) files which means new functions should be easy to add. I included the source for the F# tool that performs this task.

The rest of the code is just a shell around the interop static methods.

Following Pavan's advice, the garbage collector is called following a similar behavior to your R wrapper.

I added a copyright at the top following the JS wrapper but honestly I don't know if that's customary since most of my expertise has been with closed-source projects.

I include two example projects using the library, one in C# and one in F#

pavanky commented 8 years ago

Closing the issue because @royalstream has already done enough work on this.