That's an important point, and subjective too.
I like my code to look as much as possible like english : i like when i just read it and it says what it does. Without having to remember that some letters are just here to give technical information, so "you have to try to imagine that they are not there."

I tried to use _ref. Then i tried using _hash and _list, but it didn't work for me : the code becomes less readable. I don't like: 

$age_of_hash->{Sam};

[download]
Sam is not a hash.

Then i tried prefixes instead of suffixes, and i liked it better : i know that $h_ corresponds to %, and it doesn't get in the way so much. The beginning of a variable name feels (to me) like the right place to say its type. 

$h_age_of->{Sam}

[download]
feels better.
I even thought of using capital letters : 
$H_age_of->{Sam}
$L_items->[2]

[download]
I think i like these.
It doesn't make the "forgetting an arrow mistake" as obvious as suffixes, but it's better than nothing, and it doesn't get in the way as much.

Thank you for speaking about Data::Alias. I will give it a go. The % and @ symbols make for more readable code, I was wondering if it was possible to keep them. Every little help is good to take.

~ ~ ~

Another thing i have remarked, is that i don't always know what there is in a hash, or what keys i'm supposed to use with it. For example : 

my %data_from; # File? Measurement? Experiment? etc.
my %height_of; # Furniture? Object? Person? etc.
my %results_list_for; # the keys could be almost anything

[download]
One way to deal with this is to make names more explicit. Or to add this information at the end of the hash, like this for example : 
$data_from_measurement{measurement->label()}
$height_of_furniture{$old_furniture}
$results_list_for_file{$file_path}

[download]
But it feels quite heavy to me.
What i like about it, though, is that it tells me which type of key is expected in the hash, and what the hash could contain, too. It does tell me a lot. I might use it in some occasions...

Maybe that a different style is better in different contexts... Spinach for thoughts.

It take lots of effort to make something easy to read, and people often don't notice it, but it does help them a lot.

In reply to Re: Perl Best Practices for naming variables by mascip
in thread Perl Best Practices for naming variables by creamygoodness

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.