Re^2: Why Module::Build?

Where is all this coming from? Building modules that use C libraries or XS is fundamental to the value and success of Perl. It will never go away, nor should it.

It also wouldn't make this problem go away, since the problems people usually run into with MakeMaker are related to things like installing a config file or dealing with optional modules well, and the situations Schwern pointed out where PREFIX behaves in unexpected ways.

Comment on Re^2: Why Module::Build?

Replies are listed 'Best First'.
Re: Why Module::Build? by jonadab (Parson) on May 20, 2005 at 20:47 UTC
Building modules that use C libraries or XS is fundamental to the value and success of Perl. Yes, because Perl5 isn't very capable of doing certain kinds of things without that crutch. I'm not saying that I want hooking up C code to become impossible with Perl6; I'm saying I want it to become unnecessary. It also wouldn't make this problem go away, since the problems people usually run into with MakeMaker are related to things like installing a config file I am confident in stating flat-out that there is no portable way to do this, so it's not something that better module building code can solve. "In adjectives, with the addition of inflectional endings, a changeable long vowel (Qamets or Tsere) in an open, propretonic syllable will reduce to Vocal Shewa. This type of change occurs when the open, pretonic syllable of the masculine singular adjective becomes propretonic with the addition of inflectional endings." — Pratico & Van Pelt, BBHG, p68	[reply]
Re^2: Why Module::Build? by perrin (Chancellor) on May 20, 2005 at 21:09 UTC
Yes, because Perl5 isn't very capable of doing certain kinds of things without that crutch. No, because there are lots of great C libraries out there and no good reason to rewrite them in Perl. Also for performance reasons. C libraries are not going away, so make peace with them.	[reply]