I've uploaded Inline::CPP v0.39 to CPAN.
This version includes everything from 0.38_004 (dev), plus some new
tests such as Test::POD::Coverage, and Test::Kwalitee. It also
includes a lot of refactoring following Michael Schwern's "Skimmable
Code" talk's suggestions. The refactoring is still a work in progress
(info(), wrap() are next), with a goal of rendering the code easier to
work with in the future. Additionally there have been some
adjustments to Makefile.PL targeting more thorough META.* files
(dependencies, license, minimum Perl version). Configuration
information is also no longer written directly to CPP.pm. Now it's
written to Inline::CPP::Config.pm which is used by CPP.pm. It just
seemed cleaner.
The reasons for releasing 0.39 as opposed to another dev release
essentially all boil down to it being a good place to plant ones feet
before moving on to new development tracks:
Testing seems to have stabilized: We're not breaking anything new
(famous last words?).
There have been a lot of code quality improvements that needn't be
held back from general use.
I want to start a new development track working on refactoring the
compiler and libs guess logic in Makefile.PL, and want to establish
v0.39 as a usable base in case my Makefile.PL refactoring breaks
something in an upcoming dev release.
By the way: Does anyone know a "best practice" for where example code
should go within a distribution? ./examples/ perhaps?
--
David Oswald
daosw...@gmail.com
