I uploaded a new version of Unix.pm. I tried to address my critics in a polite and reasonable fashion and also made the changes to the distribution that they suggested.
It's still called Unix and isn't Unix specific. It still lives in the top-level namespace. Ah well.
But but but
metaperl on 2003-09-03T01:24:52
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
clscott on 2003-09-03T02:53:59
Usually the CPANites don't like it when you take _the_ top level namespace because other people come along and sayUNIX::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."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".Re: Interface
What's unixy about using the word UNIX to get a new pipe? I'd have called it PIPE or redefined "|" if I wanted to be obscure.P.S. Please don't compare this module with Quantum::Superpositions.
Re:But but but
metaperl on 2003-09-03T04:52:53
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 Re:But but but
samtregar on 2003-09-03T03:52:25
Maybe you should call it "Sh" if you mean to invoke some kind of comparison between your module and the traditional Unix shell, "/bin/sh". At least that would be unlikely to be of use to anyone else!The problem with taking UNIX.pm for this purpose is that UNIX.pm should be a module that helps you access Unix. The only reason it doesn't exist already is that Perl is already really good at doing Unixy things...
Please consider renaming your module. Your reputation as a member of the CPAN community is at stake.
-sam
Re:But but but
metaperl on 2003-09-03T17:07:37
The only thing with "Sh" is that it creates a new top-level namespace and I have never done that to date... I *occupied* the top-level of Unix by creating this module, but I did not create one.
I already have a poor reputation in the Perl(monks)? community and hope to transition to teaching middle/high school math one day. The great thing about teaching Algebra I was that I had complete command of the subject matter. The six weeks I spent teaching high school were the best 6 weeks of my life.
The only problem is the test to qualify to teach math is ridiculously hard... they don't test on high school math at all.
But anyway, I will remove Unix.pm and rename it Acme::Sh.Re:But...
drhyde on 2003-10-24T14:05:18
I note that no-one bitched at me when I put NestedMap in the top level.Re:But...
richardc on 2003-10-25T14:10:54
I did, but you chose not to pay attention.
Re:Perl Preprocessor
metaperl on 2003-09-03T16:59:52
wow that looks excellent. i wonder why larry opted for the CPP over m4...
however, I have just created a new thing I want to do with this module that would be hard with macros.
