Alan W. Irwin wrote:
> On 2008-12-03 17:09-0700 Doug Hunt wrote:
> 
>> Hi Alan, Jerry, PLplot list.
>>
>> I just started updating the perl/PDL examples for plplot and have run into
>> a question.
>>
>> I updated x02.pl to clean it up and add the second plot that was missing
>> (I have not checked anything into SVN yet). In order to make this work, I
>> also had to update the PDL::Graphics::PLplot driver, which is part of the
>> PDL distribution to add interfaces for some plplot routines not included
>> before.   A new PDL version is not likely to be forthcoming for a while,
>> at least several months, perhaps a year.

I would like to see PDL point releases to be "less major".
Every two years is not so snappy... :-)

As a model going forward, we could issue a developers release
of PDL-2.4.4_xx and see how it fairs with testing.  If no
breakage, then we could push out an official release after.

>> I also maintain a stand-alone version of PDL::Graphics::PLplot on CPAN, so
>> I could put the required interface changes there.
>>
>> My question is this:  Would it be better to have complete perl/PDL
>> examples which depend upon an external PDL module from CPAN, or would it
>> be better to have incomplete examples that are compatible with the latest
>> PDL release?
> 
> I suggest the former, "complete perl/PDL examples which depend upon an
> external PDL module from CPAN".  Once that work is completed, I would be
> willing to take responsibility for changing our build system to test for the
> CPAN version of PDL and change the list of examples in test_perl.sh.in
> appropriately depending on whether the current official PDL release or the
> CPAN version is available.

One of the ideas for PDL development going forward is to move
to a more modular architecture rather than one big blob.  That
would allow for better testing and support for the components
rather than waiting for enough steam for a full PDL release.

Functionality that is decoupled from the core PDL implementation
should be developable and releasable independantly from the PDL
core.  Implementing the separate solution will provide a good
data point on these ideas....even if the release cycle for PDL
as a whole is tightened.

--Chris


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

Reply via email to