Re^3: 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"};
[download]

Comment on Re^3: Perl Best Practices for naming variables Download Code

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	[reply] [d/l]
Re^5: Perl Best Practices for naming variables (sv, av, hv) by Anonymous Monk on Nov 09, 2012 at 04:49 UTC
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	[reply]
Re^6: Perl Best Practices for naming variables (sv, av, hv) by tye (Sage) on Nov 09, 2012 at 05:00 UTC
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	[reply]
Re^7: Perl Best Practices for naming variables (sv, av, hv) by Anonymous Monk on Nov 09, 2012 at 08:00 UTC


The stupid question is the question not asked
	PerlMonks