use Perl

• What about 'from' (Score:1)

  by Arador (8415)

  What about from?

  use from 'Spreadsheet::ParseExcel' => qw(
        Workbook
        Worksheet
        Font
        Format
        Cell
        FmtDefault
);

  Or something else that looks more like English.
• Shrug... (Score:2)

  by Matts (1087)

  Personally I don't think it's really any cleaner. You've just hidden your meaning behind another statement, another module that the next maintainer has to go and read the docs for to figure out what it does. Sure it's a bit of extra typing, but you only do it once per file.
• Thumbs down (Score:1)

  by Alias (5735)

  I think it adds complexity and reduces clarity just to save a few characters.
• Simpler syntax (Score:1)

  by davegaramond (3597)

  Actually I kinda like it since I hate all repetitions/duplications and regard them as evil.

  But it needs the simplest syntax possible to avoid burning extra brainpower. Somehow all the above examples don't cut it.

  How about supporting Unix shell's feature? And how about the name multi or many? use many 'A::{B,C}::{D,E}';
  • Re: (Score:1)

    by davegaramond (3597)

    Another example: use many 'A::B::*'; . Having to require '/somedir/*.pl' comes up from time to time for me, though quite rarely.
  • Re: (Score:1)

    by Aristotle (5147)

    I hate all repetitions/duplications and regard them as evil.

    Please see Incidental Redundancy [blogspot.com].
• Sorry (Score:2)

  by vek (2312)

  The original code is instantly understandable and the intent clear. Now when someone reads your new packages code, they have to pause for a few seconds to figure out what it does and why. I'm not entirely sure that extra speed bump is worth it.
• Hmm... (Score:1)

  by xsawyerx (8978)

  with qw(
      Teleweb::Mapper::OS
      Teleweb::Mapper::Ifaces
      Teleweb::Mapper::MainIP
      Teleweb::Mapper::HostingType
      Teleweb::Mapper::RAM
      Teleweb::Mapper::CPU
      Teleweb::Mapper::Apps
      Teleweb::Mapper::Services
      Teleweb::Mapper::Server_app
  );

  Would be:

  # extrapolates from Teleweb::Mapper
  use from 'Teleweb::Mapper' => qw(
    OS Ifaces MainIP HostingType RAM CPU Apps Services Server_app
  );
• restricted ability to search (Score:2)

  by jmm (276)

  find srctree -type f | xargs grep Spreadsheet::ParseExcel::Font
  
  The suggested kind of shorthand makes it really hard to do custom searches of your code base, such as for all the code that might happen to use a particular module.  (There might be many modules named mumble::Font - when you separate Spreadshht::ParseExcel unto a separate line from Font you lose the ability to find that unique name using generic tools.
• Wildcard? (Score:2)

  by djberg96 (2603)

  use Spreadsheet::ParseExcel::*;

  What, too Java?
  • Re: (Score:2)

    by Ovid (2709)

    Something I had considered once but was quickly talked out of. Basically, even many Java people admit that this construct was a mistake. You're not being explicit about what you want and it's therefore unclear what you get. Hell on maintenance programmers.
• Module::Find (Score:1)

  by jdv (7306)

  Why reinvent the wheel?
  • Re: (Score:2)

    by Ovid (2709)

    Same problems as listed in this proposal [perl.org]. I think, given the comments, I won't do it. Other can if they want :)