Front page | perl.perl5.porters |
Postings from September 2011
<URL: https://rt.cpan.org/Ticket/Display.html?id=69318 > On 2011.9.29 2:26 AM, Zefram via RT wrote: > EU:CB is poor on this aspect of linking. See, for example, the gyrations > that I go through with Devel::CallChecker and Scope::Escape::Sugar, > where the latter imports functions from the former. (This because I use > Module::Build, which uses EU:CB.) Having got this to work with chewing > gum and baling wire, the next step, which I haven't yet attempted, > is to build good interfaces for this into EU:CB and M:B. You're absolutely correct that CBuilder will not be able to do things MakeMaker can. And vice versa. I imagine plotting CBuilder and MakeMaker's respective strengths/weaknesses/bugs would make an interesting Venn diagram. Building that diagram isn't necessary right now, but it will be very necessary later. Now, if I'm wrong and CBuilder fundamentally can't do what MakeMaker does, apples and oranges, that's a different matter and should be brought to immediately. I would rather transplant MakeMaker knowledge into CBuilder for others to benefit from than to continue to patch MakeMaker's mess that nobody else can use or understand or test. [1] CBuilder is a separate package which has an interface and is in active use. Internals can be fixed. That's progressing Perl, not just running to stay in the same place. [1] This is the point where somebody will point out that on odd Thursdays while sacrificing the third born of a rooster that crows backwards, you can use MakeMaker's compiler code in other libraries. Great.Thread Previous | Thread Next