JavaCL 1.0.0-RC1 released : switched to BridJ, added FFT utils and UJMP matrices, bugfixes, API updates…

[Olivier Chafik]

Hi all,

After a very long wait (sorry about that), here's finally the first Release Candidate for JavaCL 1.0 !

The (important) release notes are here :

http://ochafik.com/blog/?p=615

Please beware : the BridJ port of JavaCL is now the default version (the JNA version is still available, with the "-jna" suffix on the Maven artifact), and you'll have to perform some small migration work to use it if you've already got JavaCL code :

http://code.google.com/p/javacl/wiki/MigratingFromJNAToBridJ

Also, there is now a small tutorial for JavaCL (suggestions or contributions are welcome to enhance it) :

http://code.google.com/p/javacl/wiki/GettingStarted

Feedback is always welcome, but this time it's gonna be more important than usual : I need your help to finalize version 1.0 out of this Release Candidate (and hopefully there won't be many more candidates before the final release ;-))

Cheers
-- 

zOlive

http://ochafik.com

http://code.google.com/p/nativelibs4java/

[Kazó Csaba]

Hi Olivier,


Cheers for your great work! Very exciting, getting closer to 1.0.

I've updated my little JavaCLPP library to the release candidate. It went quite smoothly, the changes to the API make it feel more coherent. The Pointer class, which I'm really getting to know for the first time, is feature-rich and in general seems more comfortable to use than the NIO buffers.

So I'm quite happy with the changes, and thank you for making it all happen!


Csaba

[jcpalmer]

Olivier,
Being that Java 7 is close, and JavaCL uses external resources, you
might look into some minor changes for 1.0 that make using Automatic
Resource Management easy to switch to.

FYI, my impression of ARM's improvement over finalize() is: finalize()
called at garbage collection (irrelevant timing for external
resources) & can also be ignored by Java implementations. Tried to
find a good link, but failed. Guess I'll have to rely on my limit
knowledge.

ARM is based around the new interface Disposable, which has the
method: public void dispose(). You might implement your own clone of
the Disposable interface, & import it where needed.

Then put the code ,currently in your finalize(), in dispose() & call
dispose() from finalize(). For a Java 7 build have your Disposable
extend Java 7's.

Just something to think about.

Jeff

[Olivier Chafik]

Hi Kazó,

2011/6/23 Kazó Csaba <kazo...@gmail.com>

Cheers for your great work! Very exciting, getting closer to 1.0.

Thanks !

 

I've updated my little JavaCLPP library to the release candidate.

Excellent !

Btw, I've added a "Who's using JavaCL" page :

http://code.google.com/p/javacl/wiki/WhoUsesJavaCL

 

It went quite smoothly, the changes to the API make it feel more coherent. The Pointer class, which I'm really getting to know for the first time, is feature-rich and in general seems more comfortable to use than the NIO buffers.

So I'm quite happy with the changes, and thank you for making it all happen!

Cool, thanks for your kind feedback :-)

 

Cheers

[Olivier Chafik]

Hi Jeff,

2011/6/23 jcpalmer <jeffrey....@gmail.com>

Being that Java 7 is close, and JavaCL uses external resources, you
might look into some minor changes for 1.0 that make using Automatic
Resource Management easy to switch to.

That's an excellent suggestion, I've added an enhancement request to the tracker :

http://code.google.com/p/nativelibs4java/issues/detail?id=72

(please all feel free to add your comments on it !)

 

FYI, my impression of ARM's improvement over finalize() is: finalize()
called at garbage collection (irrelevant timing for external
resources) & can also be ignored by Java implementations.  Tried to
find a good link, but failed.  Guess I'll have to rely on my limit
knowledge.

ARM is based around the new interface Disposable, which has the
method: public void dispose().  You might implement your own clone of
the Disposable interface, & import it where needed.

Either that, or we'll release a separate package for JDK 7 features... tough decisions to make, but fortunately JDK 7 is not quite out yet ;-)

Cheers