Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re^2: RFC: Idiom for named read-write arguments (aliases) instead of using $_[0] etc

by LanX (Chancellor)
on Sep 02, 2012 at 00:11 UTC ( #991218=note: print w/replies, xml ) Need Help??

in reply to Re: RFC: Idiom for named read-write arguments (aliases) instead of using $_[0] etc
in thread RFC: Idiom for named read-write arguments (aliases) instead of using $_[0] etc

Thanks for your well thought reply.

Can't say much about the literals and the missing error, I think swapping literals doesn't make much sense ... (well maybe in LISP).

Anyway much of your reasoning is about manipulating arguments is bad practice.

Actually perl has plenty of bultins which do that and many lamda-patterns use this feature (i.e. map/grep {BLOCK} like commands where at least $_ is aliased) and if you look closely into perl6-signature you will find the attribute "rw" for exactly this purpose.

So I can understand if manipulating aliases is not OK for _your_ coding practice, but perl is a multi-paradigm language, where other want to implement their own patters.

For me using two $-sigils like in "$$a" is indication enough that this is no normal assignment, and certainly better to read and more obvious than spreading $_[n] around a 50 line long sub.


I can show you old CORE modules which are programmed w/o unpacking variables and are very hard to maintain. Automatically refactoring $_[n] into $$name would instantly work, even on LHS of assignments and improve readability.

Cheers Rolf

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://991218]
[1nickt]: Yaerox probably best to whip up an SSCCE demonstrating the failure in what you have now and post to SoPW as a question.
[Corion]: Yaerox: That's a somewhat hard problem. Encode solves the conversion part, but for guessing what encoding a file is in, that's the hard part
[Corion]: Yaerox: There is Encode::Guess, but that needs a limited set of inputs, and it also cannot handle multiple single-byte encodings
[Corion]: If you have a BOM, that's a really easy way to recognize UTF-8. Otherwise, you can try to decode a file from UTF-8, and if that works OK and doesn't crash, most likely the file was valid UTF-8
[Corion]: But as "ansi" (Latin-1?) is a single-byte encoding, any file is a valid ANSI file

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (10)
As of 2017-03-28 13:13 GMT
Find Nodes?
    Voting Booth?
    Should Pluto Get Its Planethood Back?

    Results (332 votes). Check out past polls.