I believe you’ll want: * a nice simple build system (possibly based on the upcoming EUMM XSMULTI change) * to release early and often * to master the art of git rebasing branches rather than merging
From: Chris Marshall Sent: Sunday, December 14, 2014 4:31 PM To: pdl-porters ; [email protected] ; Chris Marshall Subject: [Pdl-porters] PDL::Tiny --- what should be in it? To support POGL2 development (updating Perl OpenGL bindings to APIs 3.x, 4.x, and the ES variants) and as a start at the PDL3 core implementation, I'm preparing a PDL::Tiny module and am looking for your input on what you think should or should not be in it. Here are my general thoughts so far: a.. The basic PDL::Tiny object starts with Moo a.. This allows full meta-object programming via Moose b.. Interoperable with state of the art perl OO programming c.. KISS principle is satisfied b.. Additional capabilities would be added via Roles a.. Data allocation b.. Data types c.. Computation support d.. Threading/vectorization c.. PDL::Tiny should interoperate with PDL-2.x a.. Using PDL::Objects support b.. Allows PDL-2.x and PDL3 options c.. Perhaps a pure-perl implementation This will give a concrete platform with which to develop PDL3 concepts. In addition, I plan to set up a github project for this effort so I can come up to speed with that platform and to encourage rapid development. I welcome your thoughts and suggestions Regards, Chris (with my PDL3 and POGL2 hats on) -------------------------------------------------------------------------------- _______________________________________________ PDL-porters mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
