Craig A. Berry wrote: > On Sat, Jun 6, 2009 at 12:28 AM, Michael G Schwern <schw...@pobox.com> wrote: > >> I'd like to somehow test for this issue without having to shove MakeMaker >> into >> bleadperl and build it on multiple OS'. [1] > > To me that sounds easier than the alternatives. How hard would it be > to fork blead on github, merge in development releases of MakeMaker, > and test MakeMaker in situ rather than relying on a lot of complicated > simulations?
Funny you should ask. http://github.com/schwern/perl/tree/ExtUtils-MakeMaker The idea there is to develop MakeMaker straight out of a bleadperl fork. That way anyone can test it, and it keeps in sync with MakeMaker changes from p5p. I did the experiment months ago. The hard work is done but its being merged is stalled until 5.10.1 goes out. > You may need less simulation rather than more, but if you want to > pretend you don't have dynamic loading when you actually do, something > like the following should do the trick: > > $ perl -e "BEGIN {require DynaLoader; *DynaLoader::dl_load_file = 0;} > use Filter::Util::Call;" Excellent, thank you! Now what needs to be done is write up a miniperl test. Possibly just be slicing out bits of basic.t (which could use some slicing). -- 164. There is no such thing as a were-virgin. -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army http://skippyslist.com/list/
