All-

This is another CPAN developers release from the
current PDL git.  It includes the newly refactored
PDL Doc stuff using core Pod::Parser rather than
the legacy forked version.  An extension to the
PDL::PP to allow for enhanced POD documentation
in PDL::PP code definitions.  Thanks to Joel and
David for the work that made these possible!

As for status of the upcoming PDL-2.4.12 release:
- still planned for mid-Feb 2013
- goal of ASPerl build farm success
- whatever enhancements get in by week 1 of Feb

Enjoy!
Chris for the PDL Developers



Release Notes for PDL 2.4.11_004 --------------------------

General Notes:

 * Another quick CPAN developers release

   - It is a snapshot of the current git development tree
     and everything may not work correctly or have complete
     documentation.

   - These release notes may not be fully complete.  Please
     see Changes (from the git log) for full details.

   - All tests may not pass, especially ones corresponding
     to issues in Known_problems.

   - Manual build/install is recommended although the
     cpan shell may be used by specifying the distribution
     path rather than just the module name, e.g.:

       cpan> get  CHM/PDL-2.4.11_004.tar.gz
       cpan> make CHM/PDL-2.4.11_004.tar.gz
       cpan> test CHM/PDL-2.4.11_004.tar.gz
       cpan> look CHM/PDL-2.4.11_004.tar.gz

Highlights:

 * Added new FullDoc key to PDL::PP to make writing CPAN
   friendly .pd files much, much easier.

 * Newly refactored docs engine using core perl modules
   rather than local PDL ones.

 * Enhanced doc support for PDL::PP and some doc cleanup

 * Fixed a problem with multiple windows and imag2d and
   imag2d_update.

 * t/gd_oo_tests.t now skips tests for OpenBSD platforms
   to avoid many failures on CPAN Testers smokers.  If
   you can reproduce this problem (sf.net bug #3518190),
   help to debug would be greatly appreciated!

_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to