use Perl

• NEVER BEGIN WITH H2XS! (Score:2)

  by schwern (1528)

  See the light as I did. If you're not using XS, h2xs is just baggage. Write a little script to do:
  
  cd /path/to/your/devel/dir
  mkdir Some-Module
  cd Some-Module
  mkdir -p lib/Some/
  cp /path/to/templates/Module.pm lib/Some/Module.pm
  perl -i -pe 's/Module::Template/Some::Module/g;' lib/Some/Module.pm
  mkdir t
  cp /path/to/templates/t/test.t t/Some-Module.t
  perl -i -pe 's/Module::Template/Some::Module/g;' t/Some-Module.t
  cp /path/to/templates/Makefile.PL
  perl -i -pe 's/Module::Template/Some::Module/g;' Makefile.PL
  perl Make
  • Re:NEVER BEGIN WITH H2XS! (Score:2)

    by Matts (1087)

    Even if you're doing XS, h2xs is baggage. I've never created a single module where I used the XS code auto-written by h2xs. Just drop in a .xs file to the mix and it gets compiled automatically by ExtUtils::MakeMaker, so why bother.
    • Re:NEVER BEGIN WITH H2XS! (Score:2)

      by schwern (1528)

      "Just drop in an [sic] xs file into the mix" is sort of like saying "Just rebuild your carburetor".
      • Re:NEVER BEGIN WITH H2XS! (Score:2)

        by Matts (1087)

        True. And? :-)
  • Re:NEVER BEGIN WITH H2XS! (Score:2)

    by Ovid (2709)

    That is so much cleaner and more maintainable. Thanks!