use Perl

• But... (Score:2)

  by Simon (89)

  It's still called Unix and isn't Unix specific. It still lives in the top-level namespace. Ah well.
  • But but but (Score:1)

    by metaperl (1904)

    the new docs do state it was so-named because it was inspired by Unix, particularly the power that its shell holds. For me, when Quantum::Superpositions came out, I didn't know what it was and its named misled me to think it had something to do with physics. But now, it is clear that it is *inspired* by physical quantum superpositions, but in actually it might be more accurately named List::Conditional or List::Cases But what name should this have which addresses your two concerns above?
    • Re:But but but (Score:2, Insightful)

      by clscott (4354)

      Usually the CPANites don't like it when you take _the_ top level namespace because other people come along and say

      "Damn, I wanted to release my module as UNIX::Foo, but now I have to co-ordinate with this guy because he owns the UNIX namespace. I guess I'll have to release it as Foo so I don't have to deal with that hassle".

      UNIX::Process::Pipeline or UNIX::Shell::Pipe would be a more suitable names and won't cause the same kind of pain as squatting on the top level.

      Re: Interface
      What's unixy about u
      • Re:But but but (Score:1)

        by metaperl (1904) on 2003.09.02 23:52 (#23768) Homepage Journal

        I'm not sure I see what the hassle is with occupying the top-level ... from a build perspective, if someone wants to create Unix::Foo and also have Unix installed, then there is simply a directory called $PREFIX/Unix made for him and Foo.pm put in it. And my Unix.pm would reside in $PREFIX

        Reply to This

        Parent