develooper Front page | perl.perl5.porters | Postings from January 2012

Re: [perl #108470] Term::ReadLine should use AE instead of Tk forevent looping

Thread Previous | Thread Next
From:
Vladimir V. Perepelitsa
Date:
January 19, 2012 09:43
Subject:
Re: [perl #108470] Term::ReadLine should use AE instead of Tk forevent looping
Message ID:
CAOgz_5_BE68da5v0gurkoPJojoeSdR2b7aJ-MWuxjnxEUM+opQ@mail.gmail.com
>
>
> It is also not Perlish to prevent someone from doing something that
> they want to do because you don't think its a good idea. That is up to
> the consumer of the module to decide.
>
>
That's a bit another problem.
Let's look: I'm a user of AE and IO::Async. I don't know about possible
problems when I will use them together.
So, from point of user I rather say thanks to Marc for warning me (maybe in
a too strict way: warn would be enough), than to Paul for anyevent brokage
(possible) without warning.

So I respect that point of author. And if I'm an author of "gun", then I
will try to protect user from "shells", which should be loaded via barrel,
instead of lock.

Of course, there are some smart users of our modules, that will do things
right and will not cry "A-a-a, that module is bad", just because something
was used wrong. But unfortunatelly there are much more such users (


> It seems to me that if the module warned, perhaps something like "You
> have loaded ... prior to this module, which is known to cause
> instability in other things using this module. Please do not report
> bugs about problems you might encounter" then it would be pretty
> reasonable.
>


> But forbidding someone to use a module because you want to use another
> module the author does not approve of seems pretty unreasonable to me.
>
>
Completely agree


> > If I know, that something on CPAN will not work, or will work badly with
> my
> > module I prefer to protect from such interaction.
>
> If that is your attitude you should hide your code away and make sure
> that anyone that uses it signs a contract about terms of use. But that
> also means it doesn't belong on CPAN and isn't really what I would
> call "free software". AnyEvent is released under the same terms as
> Perl itself. Therefore it is "free software". Therefore anyone can
> take the code and do pretty much whatever they want to it. But they
> can't do the same with the version on CPAN, doesn't that strike you as
> being the antithesis of "free software"?
>
> It simply is not YOUR problem what happens when someone decides to do
> something you think is stupid with your code. It is that persons
> problem. Trying to forbid people from doing something you think is
> stupid just means you are going to stop someone smarter than you doing
> something smart that you never thought of. This actually seems like a
> good example of that.
>
> > Just try to talk with him and many users of AE and IO::Async will win
> > instead of stupid war between AE and IO::Async
>
> Of course it is always better to talk about things. Hopefully they can
> figure something out.
>
> cheers,
> Yves
>
>
>
>
> --
> perl -Mre=debug -e "/just|another|perl|hacker/"
>



-- 
Best wishes,
Vladimir V. Perepelitsa aka Mons Anderson
<inthrax@gmail.com>, <mons@cpan.org>
http://github.com/Mons

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About