Re^8: [JOB] The Perl Foundation seeks Windows Developer

Heh! Well, that goes to show that TIMTOWTDI still applies!

In this specific example, I wouldn't use DDS in practice because I'm trying to limit dependencies to 5.8 core modules only.

Once Class::InsideOut reaches its 1.0 release, I was going to requiest that a PPM be generated in the University of Winnipeg PPM repository anyway.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

Comment on Re^8: [JOB] The Perl Foundation seeks Windows Developer Download Code

Replies are listed 'Best First'.
Re^9: [JOB] The Perl Foundation seeks Windows Developer by demerphq (Chancellor) on Apr 03, 2006 at 12:01 UTC
What I would do in this situation is fake it. Set it up so on 5.8.0 or whatever weirdo version AS is using DDS becomes a prereq. Then structure your code so you use refaddr from either source. That should get it sorted enough to distribute through their infrastructure, and shouldn't really affect normal users. I reckon only a little bit of Makefile.PL magic would be required. Just do a check like `( $^O eq 'MSWin32' && eval "use Scalar::Util qw(refaddr); 1") ? ( 'Data::Dump::Streamer' ) : ()` [download] --- $world=~s/war/peace/g	[reply] [d/l]
Re^10: [JOB] The Perl Foundation seeks Windows Developer by xdg (Monsignor) on Apr 03, 2006 at 15:50 UTC
I might yet do that for `Class::InsideOut`, but I don't think that's a really good long-term fix. A quick spin through Module;:CoreList shows 299 of 359 modules in the perl 5.8.8 core being new or changed since 5.8.0 -- who knows what kind of differences are lurking. Keeping track and finding/writing proxies anytime I use a core module is more headache than I'd like. I'd much rather be able to specify an up-to-date core module as a requirement and be done with it. -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply] [d/l]