Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Re^3: Perl Best Practices for naming variables

by Anonymous Monk
on Nov 08, 2012 at 12:04 UTC ( #1002883=note: print w/replies, xml ) Need Help??

in reply to Re^2: Perl Best Practices for naming variables
in thread Perl Best Practices for naming variables

There sure is more than one way to name your references.

$rsReally = \"yes really"; $raReally = [qw"yes really"]; $rhReally = {qw"yes really"};

Replies are listed 'Best First'.
Re^4: Perl Best Practices for naming variables (sv, av, hv)
by tye (Sage) on Nov 08, 2012 at 15:27 UTC

    In Perl, the prefixes of sv, av, and hv might be more recognizable. Well, at least for people who have seen discussions that touched on internals that used the standard (and ubiquitous) abbreviations that are used internally.

    At least, I have sometimes used names like $sv_xml when I saw a value in calling out "this is a reference (of this type)" in the variable name.

    - tye        

      Maybe, though array-value/hash-value/scalar-value don't sound as good as array-ref/hash-ref/scalar-ref -- but definitely better than ref-array/ref-hash/ref-scalar

        But ar, hr, and sr aren't any more recognizable than ra, rh, and rs (probably worse because, especially hr and sr, they are too recognizable as something else). I think aref, href, and sref would work fine. But if I want a prefix half that long, I'm going with av, hv, and sv. :)

        - tye        

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1002883]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (5)
As of 2018-05-20 09:37 GMT
Find Nodes?
    Voting Booth?