Skip Menu |

This queue is for tickets about the IPTables-ChainMgr CPAN distribution.

Report information
The Basics
Id: 64874
Status: resolved
Priority: 0/
Queue: IPTables-ChainMgr

People
Owner: Nobody in particular
Requestors: ratner2 [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 0.9
Fixed in: (no value)



Subject: Outdated POD example using indirect syntax
Outdated POD example using indirect syntax. Suggested change to: my $ipt_obj = IPTables::ChainMgr->new(%opts)
Do we have a language police now?
RT-Send-CC: andk [...] cpan.org
No, we don't. However, we do have caring people looking out for their peers. People, who might've learned about the caveats of indirect object notation the hard way and seek to spare otheres from the same suffering, or people that, albeit realising that there's more than one way to do it, believe that consistency is not a bad thing either and think that following the footsteps of the perl core, which, some while ago, eliminated a lot of indirect object notation in many parts of the core documentation, is a good thing and improves documentation's accessability and the quality of our perl ecosystem in general. While this is certainly not any kind of real bug, I believe it still is an entirely valid wishlist item that our community should be open to. No one would possibly object to this ticket being rejected because the author's personal preference happens to be indirect object notation. However, calling people names, which is what I consider calling people "syntax police" to be, isn't going to improve things, but, in the worst case, drive people away. I hope that isn't what will happen here.
But indirect object notation is not outdated. It is grossly wrong to say so. It's part of the language and is neither deprecated nor subject to a deprecation cycle. I would not mind if a movement existed that would fight a battle to get indirect object notation deprecated. There would be pros and cons and public discussion and I would participate. Or maybe I just didn't get it that the poster and the author of the module are familiar with each other? Is it just a memo quasi to self? It's impossible to tell, that's why I had the impression I had to intervene. What I wanted to say is, please, please, be careful to let the authors and maintainers on the cpan the freedom they deserve to do things the way they prefer it. IF you feel the urge to argue with them about bikeshed issues, make it clear what exactly is at stake and mark your requests as wishlist items. This one does not appear to me as wishlist item. Severity is "normal" as far as I can see.
Show quoted text
> This one does not appear to me as wishlist > item. Severity is "normal" as far as I can see.
My bad. Sorry.
I've switched over to direct syntax for 1.3 (should appear on CPAN shortly).