Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I might find it more beautiful if there was an explicit import:

    use LWP::Simple 'get'

    What happened to the mantra from Exporter.pod?

    "Do not export anything else by default without a good reason! ... Exports pollute the namespace of the module user."
    • I hate that line.

      Oh, its intentions are good. Its there to make authors think and to avoid modules like POSIX which export nearly everything. So often people only hear the "do not export anything by default" and miss the "without a good reason" part.

      If your module doesn't do anything useful but provide functions, go ahead and export some useful defaults. The user's going to have to import stuff anyway, give them a leg up. Why? Choice. Specifically the user's.

      Any module which exports by default can be
      • I appreciate your line of thinking, schwern. Thanks for clarifying.

        Personally, I have mixed feelings about it. Some default exports can be handy and look clean. However, I like to grep my code for a function name and be able to figure out where it came from.

        OO code tends to be traceable to the object construction. But with with procedural code, if there's no explicit export, it is more difficult to track down where a function comes from, and that can slow me down. (Yes, I know there are modules and techniqu