Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • It's still called Unix and isn't Unix specific. It still lives in the top-level namespace. Ah well.

    • 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?
      • 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

        • 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 put in it. And my would reside in $PREFIX