PDL 2.064 has just been released. Notable changes since 2.062:
- pthreads should now be available on BSD systems
- Support for signed and unsigned versions of all integers up to 64-bit, and real and complex long double
- qsortvec* now work with badvalues as documented
- wfits now handles RICE compression
- NiceSlice now works correctly with comments and strings
- rmpeg added, rpic and wpic work with multi-image PNM files
- xvals etc return at least a double, avoiding problems with e.g. byte ndarrays
- Improvements to $MACRONAME() handling including that arguments can now contain (balanced) brackets
- The PROJ.4 interface has been updated to use the PROJ v6+ interface, finally
- A zeroes() regression from 2.057_01 where it ignored the type of an input PDL has been fixed
The last dev-release showed FreeBSD 13 (the latest) failing to find “csinl” (complex long double sin). That is mandated by C99, so we won’t be doing configure probes for it. Please update your libm if this causes a problem, and your compiler (including clang <12.0.5) if it crashes on pdlcore.c.
Future plans, in something like intended order:
- “loop fusion” techniques to maximise locality of computation, minimising data’s trips through the “straw” between CPU and main RAM
- finish the independent C interface for making PDL usable from e.g. Python
- use OpenCL or other means to also utilise GPUs if available
The IRC channel (#pdl on irc.perl.org) is a great virtual place to come and ask questions, or just watch the GitHub messages flow by.
As usual, please give the new PDL a try and report problems.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
