use Perl

• another list (Score:1)

  by domm (4030)

  of dists using it:

  http://cpants.perl.org/dist/UNIVERSAL-exports [perl.org]

  Seems quite similar to what gonzui says...
  • Re:another list (Score:2)

    by schwern (1528)

    Curses! I really wish I could just break compat because dying really is the better thing to do. Maybe I'll throw in a "use UNIVERSAL::require qw(die)" or something.
    
• I wish... (Score:1)

  by perrin (4270)

  that you hadn't put it in UNIVERSAL::, but that's an entirely different issue.
  • Re:I wish... (Score:2)

    by schwern (1528)

    If it wasn't in UNIVERSAL the module wouldn't work. The require method has to exist and be in a class' inheritence hierarchy *before* the class to be required is loaded.
    
    And this really is the sort of thing which should be universal.
    • Re:I wish... (Score:1)

      by perrin (4270)

      It only has to be in UNIVERSAL because of the particular API you chose. It would be just as useful as something like this:

      Module::Loader->load($module_name);

      What bugs me about the current approach is that when I use a CPAN module that loads this, it magically adds require() methods to all of my classes, whether I want them or not.
      • Re:I wish... (Score:2)

        by schwern (1528)

        It only has to be in UNIVERSAL because of the particular API you chose.

        Yep, but I can't exactly back out of that now. Remember, UNIVERSAL::require is an implementation of a Perl 6 RFC. People started using it. Go figure.

        What bugs me about the current approach is that when I use a CPAN module that loads this, it magically adds require() methods to all of my classes, whether I want them or not.

        require() is a special case. You're highly unlikely to create a method called "require" as its already a keyw
• my vote (Score:1)

  by rjbs (4671)

  I'd love for you to fix it, or at least make it easier to get the right behavior. Otherwise, I end up writing the code that should be in there, myself.

  --
  rjbs