Re^4: Perl Best Practices for naming variables (sv, av, hv)

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

Comment on Re^4: Perl Best Practices for naming variables (sv, av, hv) Download Code

Replies are listed 'Best First'.
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
they are too recognizable as something else :) I don't have much in the way of cultural bias, but I am biased against calling a reference a value -- sure its a value, sure its common in perlapi/perlxs , but not in the perldata...	[reply]